SAGE gives Claude Code, Codex, Cursor, Windsurf, and any MCP-capable agent one local memory node: semantic recall, governed validation, encrypted storage, and a CEREBRUM dashboard built around the 3D MRI brain.
v11 is dashboard-first. The onboarding flow handles semantic memory, AI-tool connection, and setup recovery without making users edit config files by hand.
Click to copy the MCP bootstrap prompt and paste it into any agent session that can edit its project folder.



v11 links two separate SAGE nodes when they can already reach each other: same LAN, VPN, or an operator-provided route. Built-in internet/NAT traversal is planned for v11.5.
No cloud. No telemetry. No API keys phoning home. Memories live in ~/.sage/ and nowhere else.
Optional encryption at rest. If your laptop is stolen or synced to the cloud, nothing is readable.
Every memory is digitally signed. Full audit trail — verify nothing has been altered or injected.
Claude, Cursor, Cline, DeepSeek, Gemini, LM Studio, Ollama — any model, any provider.
Give your AI memory that persists across sessions, validates what it learns, and improves measurably over time.
Download SAGEmacOS · Windows · Linux · Source on GitHub
Governed institutional memory — validated by BFT consensus, scored by confidence, and decay-aware over time.
v11 makes SAGE usable from the dashboard. First-run onboarding connects your AI, semantic memory turns on through a guided local Ollama flow, the reranker installs and verifies itself, and two SAGE nodes can federate on a LAN, VPN, or operator-provided route with a human verification ceremony. Under the hood, app-v15 adds co-commit and cross-federation transaction types while preserving byte-identical replay before activation.
The 3D MRI brain is now the default view — your memories as glowing points inside a translucent brain, domains as lobes ordered by recent activity, corroborated knowledge pulled to the core. Around it: an Overview control board for the whole node, real full-text + semantic search with bulk curation, a live task board your agents and you share (with assignment and atomic claiming), and the agent-to-agent message bus as a Messages tab. A first-run onboarding wizard walks new nodes through everything — re-runnable any time from Settings.
One click in the dashboard and SAGE downloads a pinned llama.cpp build for your platform and the bge-reranker-v2-m3 model, verifies both by checksum, then starts and manages the sidecar — no terminal, no package manager, nothing leaves your machine. Recall results get re-scored by a cross-encoder for sharper relevance, and the recall depth setting now goes up to 20 with guidance that adapts to whether the reranker is on.
Link your whole SAGE to another person’s on the same LAN, or over reachability you provide. First-class internet/NAT traversal is planned for v11.5. The join ceremony verifies both sides with rotating six-digit codes (Google-Authenticator compatible), QR scans, and an unskippable mutual compare, so you know exactly who you federated with. Share only the domains you choose, at the clearance ceiling you choose; recall reaches across live, nothing is copied, and nothing is ever deleted. Revoke any time.
A guided flow turns on meaning-based recall (Ollama + nomic-embed-text), re-reads your existing memories in the background with live progress, and — if an old vault key left some memories unreadable — recovers them in place with your recovery key. Every new memory is stamped with the embedder that produced it, so the dashboard always tells you the truth about what is searchable by meaning.
Memories persist across every conversation — projects, preferences, decisions, prior outcomes. Nothing is lost between sessions.
Memories are validated before being committed. Spurious data is filtered out; corroborated data is reinforced.
Memories strengthen with corroboration and decay without reinforcement — analogous to human episodic memory.
Recall by meaning with local embeddings, then re-score with a self-installing local reranker. Everything on your machine.
Stores what worked and what failed. Published research shows agents with this feedback loop improve measurably over time.
A 3D MRI brain of your memories — domains as lobes, consolidation as depth. Search, curate, and drill into a memory’s train of thought.
Import from ChatGPT, Claude, or Gemini. Seed your AI’s memory from existing conversation history.
Built-in auto-updater checks releases, downloads, and replaces — all from the dashboard.
Link two SAGE brains on a LAN or operator-provided route with a human-verified join ceremony. Share chosen domains live, at a clearance you set — revocable any time.
Local BadgerDB/SQLite stores under your home directory. Inspect, query, back up, and move your data.
Route work between AI agents. Send research to one model, analysis to another, results back to your primary — all through SAGE.
Pipeline exchanges are summarised as memories automatically. Full audit trail of inter-agent work without storing bulky payloads.



SAGE is local memory infrastructure for AI agents. It gives tools like Claude Code, Codex, Cursor, Windsurf, and Claude Desktop a persistent memory server they can use through MCP or REST.
No. SAGE stores memories with signatures, consensus validation, confidence scoring, decay, clearance, domain permissions, full-text search, semantic recall, and optional local reranking.
On your machine by default. Memories live under ~/.sage/ in local BadgerDB/SQLite stores, with optional AES-256 encryption at rest. There is no required cloud account.
Any AI tool that can run an MCP server or call a local REST API. The dashboard can write config for common clients, and the Python package is sage-agent-sdk.
v11 adds the rebuilt CEREBRUM dashboard, first-run onboarding, guided semantic setup, a self-installing local reranker, v11 federation, and the app-v15 consensus fork.
v11 federation is LAN-first: it links two separate SAGE brains through a human-verified ceremony when the nodes can already reach each other, such as same LAN, VPN, or your own tunnel. Built-in internet/NAT traversal is planned for v11.5.
Install SAGE, paste the config into your AI client, and start working. Memory builds automatically across sessions.
Download for macOS, Windows, or Linux. Install the signed release asset and open the local dashboard.
The setup wizard generates MCP config for Claude Code, Codex, Cursor, Windsurf, Claude Desktop, and other MCP-capable tools.
Your AI uses memory tools automatically. Projects, preferences, decisions — persisted across every session.
MCP-native tools connect locally. ChatGPT uses a separate OAuth connector path, so SAGE includes a guided setup flow for the tunnel, OAuth exchange, and token issuance. A browser-extension path is available for users who prefer not to expose SAGE over a tunnel.
Changing AI providers shouldn't mean starting from zero. SAGE is model-agnostic — your data belongs to you.
Export conversations from OpenAI, then import into SAGE.
Export Claude.ai conversations and import them.
Export via Google Takeout and import.
SAGE starts as one local brain. When you need a team across projects, machines, or an organization, add agents from the dashboard.
Add, configure, and manage agents from the dashboard. Each gets its own signing keys, identity, role, and permissions.
Per-domain read/write permissions with a visual matrix. Five clearance tiers from Guest to Top Secret.
Each project folder receives its own Ed25519 keypair automatically. No shared keys, no manual setup. One CLI command claims a pre-configured identity.
Rotate agent keys with one click. All memories re-attributed atomically. Old keys permanently retired.
Nine-phase state machine handles chain redeployment. Backups at every phase, automatic rollback on failure.
Every memory tracks which agent created it. Admin agents are marked in the dashboard. Filter the brain view by agent.
Create an agent in the dashboard with name, role, and RBAC permissions. Get a one-liner. Run it in your project folder. The agent claims its pre-configured identity automatically.
Add an agent with name, role, clearance level, and domain permissions. The dashboard generates a claim token.
sage-gui mcp install --token XXXX
Run this in the project folder where your AI works.
The agent connects with the correct identity, role, and RBAC on its next session. Everything goes through the chain.
AI agents with persistent memory get measurably better over time. Without memory, they show essentially zero improvement no matter how many sessions you run.
AI agents with memory get better over time. Without memory, they don't learn at all.
50-vs-50 controlled study: agents with governed memory outperform memoryless agents on complex tasks
Agents that learn their jobs from experience, not instructions — the “new hire” problem solved
The full architecture: BFT consensus, multi-validator, RBAC, federation — for teams and enterprises
Run SAGE as a local memory server, then connect through MCP, REST, or the Python SDK. The dashboard handles setup; the APIs stay available when you need automation.
Most “memory plugins” send your conversations to servers. SAGE runs locally, with memories stored in local BadgerDB/SQLite stores under your home directory.
No cloud accounts. No telemetry. Memories live in ~/.sage/ and nowhere else.
Local data stores under ~/.sage/. Inspect them, query them, back them up, move them.
Every memory is digitally signed with your local key. Full audit trail.
Optional encryption for the memory vault. If your machine is stolen, the on-disk memories remain unreadable.