New

Migrate

The AI changes. The context stays.

Switch AI providers without losing your project context. Your .faf file is the constant — the AI is the variable.

ChatGPT → Claude in 3 steps

Export your ChatGPT memories

Settings → Personalization → Memory → Manage → Export. You'll get a file with everything ChatGPT knows about you and your projects.

Import into Claude

Claude now supports memory imports — even on the free plan. Your imported memories become Claude's MEMORY.md. That's your RAM.

Sync

faf tri-sync

Your .faf (ROM) now syncs with Claude's memory (RAM). Project context, decisions, conventions — all persistent across every session.

Why this works

Before

ChatGPT memories

Locked in. Can't leave.

→

After

.faf + Claude MEMORY.md

Portable. Yours forever.

📁

.faf is yours — a file in your repo. No vendor lock-in. Move between Claude, Cursor, Gemini, any AI.

🔄

tri-sync keeps it alive — .faf ↔ CLAUDE.md ↔ MEMORY.md. Change one, all update. Persistent across every session.

🌐

IANA-registered format — application/vnd.faf+yaml. The only standardized AI context format. Not a hack. A standard.

Also works with

Cursor → Claude

Gemini → Claude

Claude → Cursor

Any AI → Any AI

.faf is the universal format. bi-sync keeps .faf ↔ CLAUDE.md in sync (free forever). tri-sync adds AGENTS.md, .cursorrules, GEMINI.md, and session memory.

Try it

npx faf-cli@latest score

Paste this anywhere — your terminal or your AI. Both understand it.

FAF Pro

tri-sync from a dime a day

GitHub

Star the repo