Brainfile is a config bundle for Claude Code. You run it inside your own Claude Code subscription — no extra API keys, no databases, no servers. Drop it in, restart Claude, go.
Brainfile runs inside Anthropic's Claude Code CLI. If you don't have it yet, install it first — it's free to download (you'll need a Claude Pro or API account to use it).
Full install instructions and platform-specific options (macOS, Linux, Windows): docs.claude.com/claude-code.
Brainfile is cloud-delivered: one command pulls the current system — the Autopilot protocol, the pattern files, and your role pack — straight into your project as plain markdown you own. Re-run it anytime to get the newest freshness feed.
Your personal pull command (it carries your license token) appears on screen the moment you start your trial, and the same command is emailed to you at checkout.
Open a terminal, go to the project where you want Claude Code to use this OS, and run your pull command (yours includes your email and license token):
You should now see AUTOPILOT.md, a starter CLAUDE.md, START-HERE.md, and a brain/ folder (including brain/freshness/) at the root of your project — every file plain markdown you can open and read.
Quit any running Claude Code session in this directory and start a fresh one:
Claude automatically loads CLAUDE.md + the rules in .claude/rules/ on the first message. To confirm everything's wired up, run:
You should see your role-specific agents (or rules, depending on your persona pack) listed. If /agents returns nothing custom, double-check that CLAUDE.md is in the same folder you launched claude from.
Ask Claude to read its new context and tell you what it knows. This is the fastest way to confirm the install worked end-to-end:
You should get a role-aware response that references the rules from your persona pack — not a generic summary. That's your signal that Brainfile is live.
The pull delivers a small set of plain-markdown files (a few dozen KB): the Autopilot protocol, a tuned CLAUDE.md, the pattern files, and a brain/ starter. No binaries, no scripts you have to trust — open every file, read every line.
.claude/rules/.claude/rules/ directory and Claude Code's auto-loading of CLAUDE.md are the mechanisms it relies on. Cursor uses .cursorrules, Windsurf uses .windsurfrules — different formats. The CLAUDE.md content itself is portable plain markdown you can adapt, but the agents/rules wiring is Claude Code only. We focus exclusively on Claude Code so every file leverages its full feature set instead of being a lowest-common-denominator configuration.CLAUDE.local.md, install Brainfile, then merge any project-specific rules back into the new CLAUDE.md; or (2) install Brainfile in a fresh sub-folder, diff the two CLAUDE.md files, and pull the sections you want. Every Brainfile file is plain markdown — there's no magic, just structured prose. Take what's useful, discard what isn't.brain/freshness/ and never rewrites your rules. Treat your installed Brainfile as your config and version it in git..claude/rules/. For example, a founder who also does marketing can copy .claude/rules/ files from the Marketer role pack alongside the founder pack. Claude Code loads every file in .claude/rules/ at session start.CLAUDE.md must be in the same directory you launched claude from (project root, not a sub-folder); (2) you may need to fully quit and relaunch Claude Code, not just start a new chat; (3) confirm .claude/rules/ exists and has files in it (ls .claude/rules/). If all three check out and Claude is still generic, email [email protected] with your terminal output.Pick your persona, drop it in, restart Claude Code. 30-day money-back guarantee on every paid plan.
See pricing & pick your persona → Try the free builder