Every conversation starts from zero. SAGE provides persistent, encrypted, consensus-validated memory that runs entirely on your machine — your data never leaves it.
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.
v10.6.0 gives an agent richer signals for reasoning over its own memory. Recall now returns how corroborated each memory is — not just a confidence number that can't tell a never-confirmed hunch from a once-solid fact that has merely aged — and a new MCP tool lets agents record how two memories relate, building a typed knowledge graph instead of a flat “related” mesh. Both surface capability the node already held but never exposed on read: no consensus rule, transaction handler, or AppHash changes, so a mixed v10.5.x / v10.6.0 cluster computes identical state.
A low confidence score was ambiguous from the number alone: a fresh, never-corroborated belief and a once-solid fact that has simply decayed under time can land on the same value — and a reader couldn't tell “never confirmed” from “confirmed once, now stale.” Every recall path (/v1/memory/query, /search, /hybrid) already fetched the corroboration count to compute that score, then threw it away; it's now returned alongside — and threaded through the MCP recall tool — so agents doing uncertainty or gap detection can tell the two apart. No new store read, no scoring change.
sage_link, #46)The node's link endpoint always accepted a free-form relationship type, but the only way agents created links hardcoded them as plain “related” — so an agent could build a flat mesh but never record that one memory supports, contradicts, causes, precedes, or refines another. The new sage_link tool exposes the full vocabulary: a directional source → target edge with a caller-chosen type, passed through verbatim. Agents can finally build a typed knowledge graph over their memory rather than a related-only one.
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, not keywords. Local embeddings via Ollama keep your data private.
Stores what worked and what failed. Published research shows agents with this feedback loop improve measurably over time.
Visualises memory as a force-directed graph. Search and filter by domain, type, or agent.
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.
Customise startup behaviour. Configured from the dashboard; no config files to edit.
Standard SQLite database. Open it with any tool, query it, back it up. You own every byte.
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.






Install SAGE, paste the config into your AI client, and start working. Memory builds automatically across sessions.
Download for macOS or Windows. Double-click to install. Signed and notarized.
The setup wizard generates MCP config for your AI — Claude, ChatGPT, DeepSeek, Gemini, Cursor, or any MCP tool.
Your AI uses memory tools automatically. Projects, preferences, decisions — persisted across every session.
ChatGPT does not speak the same MCP protocol as Claude, Cursor, and Cline. SAGE ships an OAuth-based connector and a guided 6-step setup wizard that handles the tunnel, OAuth flow, and token issuance for you. A separate 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 brain. When you need a team — across machines, family members, or an entire org — 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
SAGE isn't an API you call. It's memory infrastructure — a local server your AI connects to via MCP. Build from source or use the Python SDK.
Most “memory plugins” send your conversations to servers. SAGE runs entirely local. A SQLite file in your home directory.
No cloud accounts. No telemetry. Memories live in ~/.sage/ and nowhere else.
Standard SQLite. Open it with any tool, query it, back it up, move it.
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.