One private, local memory your AI tools share. Cross-model, on-device, never lose a session.
One private, local memory your AI tools share.
Every AI you use forgets you the moment the chat ends. You re-explain the same context over and over, and when a session dies, the reasoning behind it is gone for good. Epiphany fixes that. It's a single memory that lives on your machine, that Claude, Grok, Gemini, and more all read from and write to, so what you tell one, the others already know.
Epiphany is a local MCP server plus a tiny CLI.
recall and remember.epiphany connect <tool> wires that server into each AI tool, in the tool's own config format, and installs a standing rule so the agent reaches for your memory on its own.because, builds_on, part_of, ...), and recall walks that graph to reconstruct the whole thought-string.The intelligence stays in the models you already use. The brain itself is a fast, private librarian: it holds, connects, and recalls. It never phones home.
Requires Node 18+.
npm install -g epiphany-mcp # puts the `epiphany` command on your PATH
Or build from source:
git clone https://github.com/GATSV-tech/epiphany.git
cd epiphany
npm install
npm run build
npm link
Wire it into the tools you use, then fully restart each one:
epiphany connect claude-code
epiphany connect grok
epiphany connect gemini
epiphany list # see all supported tools
Turn on the background "never lose a session" sweep:
epiphany schedule
That's it. Now talk to any connected AI. It will recall what you've told the others and save what's worth keeping, on its own.
Run epiphany with no arguments any time to open the dashboard and look inside your brain.
| Tool | Connector | Standing rule |
|---|---|---|
| Claude Code (every terminal) | auto | auto |
| Grok CLI | auto | auto |
| Gemini CLI | auto | auto |
| Antigravity (Google IDE) | auto | shared with Gemini |
| Claude Desktop | auto | guided (account setting) |
| Cursor | auto | guided (app setting) |
| Warp (terminal, Agent Mode) | auto | guided (app setting) |
| Hermes (Nous Research agent) | auto | guided (instructions) |
| Perplexity (Mac app) | guided | guided (instructions) |
epiphany connect <tool> wire Epiphany into an AI tool (connector + rule)
epiphany rule <tool> update just the standing rule for a tool
epiphany list show supported tools
epiphany dash open the interactive dashboard (browse, search, curate)
epiphany graph see your whole brain as an interactive visual graph
epiphany weave wire the reasoning connections between related memories (optional; uses your LLM key)
epiphany status show brain size, connected tools, and auto-capture state
epiphany ingest sweep session logs into the brain now (one-shot)
epiphany watch run the near-real-time watcher in the foreground
epiphany schedule install the background watcher (captures sessions as they happen)
Your brain lives at ~/.epiphany/brain.db. It's yours. Back it up, inspect it, delete it, it's just SQLite.
Epiphany's core, local cross-model memory with reasoning graphs and automatic capture, works today. Next:
Contributions and ideas welcome.
MIT.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y epiphany-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-gatsv-tech-epiphany": {
"command": "npx",
"args": [
"-y",
"epiphany-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceepiphany-mcpnpmio.github.GATSV-tech/epiphany works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.