Your Sessions Don't Belong to Claude
Your sessions don't belong to Claude. Or Cursor. They belong to you.
Every time you open a new AI conversation, you're rebuilding context that should have carried over. Your project's architecture. Your naming conventions. The decision you made last Tuesday and why. All of it - locked inside the tool that captured it, unreachable to everything else.
The Silo Problem
Every AI coding tool builds a silo.
Claude Projects stores your context in Claude. Cursor's .cursorrules lives in Cursor. Copilot's instructions sit in GitHub. Cline's rules stay in .clinerules. Start a session in a different tool - or a different machine, or a new project - and you explain everything again.
"Context is the only thing that matters. It's such an important piece of getting a language model to do anything for you." - Logan Kilpatrick, Google
The context you've built is yours. But the tools keep it hostage.
What if every coding tool you use already had your full project context - before you said a word?
One Vault. Any Agent.
fai breaks the silo. There's one vault. It's yours. And it feeds every agent.
Every time you run fai, it doesn't just configure one tool - it configures all of them. Context gets written into .clinerules, .continuerules, .github/copilot-instructions.md, AGENTS.md, .windsurf/rules/fai-context.md, .cursor/rules/fai-context.mdc, and more - all in the background, before your session even starts. You launch Claude. By the time it starts, Cursor already has your context too.
This is ambient configuration. Not a sync you have to trigger. Not a settings panel you have to open. Just: every tool, always current.
"Structure matters more than the efficacy of the tools you have." - Dhanji Prasanna, CTO, Block
Your structure is the vault. It doesn't care which tool reads it.
The 14 Agents
fai ships with 14 built-in coding agents. Pick any of them. All of them get your context.
| Mode | Agents |
|---|---|
| CLI - interactive, blocking | Claude Code, Codex, OpenCode, Goose, Aider, Gemini CLI, Amazon Q |
| GUI - launch and step away | Windsurf, Cursor |
| Extension / IDE - rules-file injection | Cline, Continue.dev, GitHub Copilot, JetBrains AI, OpenClaw |
CLI agents spawn a subprocess you interact with directly. GUI agents launch their app and fai exits - they already have your context. Extension agents get their rules file refreshed so the next time you open VS Code or JetBrains, everything is already loaded.
--agent controls which one launches. All 14 get configured.
What Stays
The vault compounds regardless of which agent ran the session.
Every session captures decisions, approaches, and context into three layers: your active session notes, your project knowledge, and your personal preferences. These don't live inside any tool. They live in ~/.fai/ - plain markdown files, readable, portable, git-optional.
"For every unit of work, you should make the next unit of work easier to do." - Dan Shipper, CEO, Every
That's the compound mechanic. Session ends. Vault updates. Next session - whichever tool you open - starts already briefed.
Switch from Claude to Cursor. Your vault follows. Try OpenCode for a day. Your vault follows. Go back to Claude. Still there. The tool is interchangeable. The context is yours.
The Invitation
You've been rebuilding context every session - for every tool - for as long as you've used AI.
fai stops that. One vault. Any agent. Context that persists and compounds regardless of what you launched.
Your sessions don't live in Claude's memory or Cursor's project files. They live in your vault. Which means they live with you - across tools, across jobs, across the AI landscape as it keeps shifting.
Build anything with AI. Keep everything. Evolve forever. This is what "keep everything" looks like in practice: 14 agents, one vault, zero silos.
Read more: What Stays When the Session Ends →