Connect · Claude Code
Give Claude Code a memory.
Everything you decide in Claude Code is remembered, and every other tool you use knows it next time. One command, nothing to configure by hand.
01 · What you get
“Supported” means three things. Here's each one for Claude Code.
Native. Every session is captured as it happens.
CLAUDE.md, global, loaded in every project.
MCP server registered.
02 · Install
One command wires Claude Code and every other tool on your machine.
- Run the installer. It creates your private data repo on GitHub, generates your key into the Keychain, and asks whether to start with your past AI sessions or fresh.
curl -fsSL https://raw.githubusercontent.com/rohithhn/Open-Agentic-Brain-and-Memory/main/install.sh | bashmacOS or LinuxNode 22+gitA GitHub account - It wires Claude Code. The installer registers the brain's MCP server, writes a ~2,000-token briefing into
CLAUDE.mdinsideBRAIN:START/ENDmarkers, and captures each session as you work. - Check it. Open a new Claude Code session and run
/mcp: the brain's tools are listed. Then ask “What should I know before working on this repo?” For a full read-only check of every tool, runbrain doctor.
03 · Questions
Connecting Claude Code
Do I need an account or an API key?
No. There's no account and no server of ours. The memory lives in a SQLite file on your machine, and travels as one age-encrypted file to a private GitHub repo you own.
Will it overwrite my instructions file?
No. The briefing lives inside its own BRAIN:START/END markers, and MCP wiring is additive: it never touches entries it didn't create.
Does Claude Code see what I did in other tools?
Yes. There's one store for every tool on the machine, and your other machines get it through brain sync and brain restore.
What platforms work?
macOS and Linux, with Node 22+, git and a GitHub account. Windows isn't supported yet.
04 · Other tools