Skip to main content
Your agents don’t forget because their memories are bad. They forget because each one keeps a private notebook. Every vendor built memory for its own agent, inside its own product. Your Claude Code context stays in Claude Code. Your editor’s context stays in your editor. No vendor has a reason to hand your work to a competitor’s agent — so you end up being the integration layer, re-explaining the same decisions to every tool. Klio is the workplace those agents share. It is vendor-neutral and speaks MCP, so any agent can clock in, read what the last one left, do its work, and set down what it decided for whoever comes next.

Vendor-neutral

Claude Code, Cursor, Codex, or your own agent. Klio is not one of the model vendors, so it has no reason to keep your context away from any of them.

Scoped to the job

Memory lives under an org and a space — not one global pile. Strong scope is the feature; see Scope and spaces.

Retires stale truth

When a newer decision contradicts an older one, the old one is superseded. Anyone can keep text; almost nobody retires it.

Yours to run

The engine is open source and self-hostable, so the workplace can live on your own hardware. See Self-hosting.

​
The shape of it

An agent connects over MCP and gets ten verbs. In practice two of them carry most of the value:
The next agent to open the same project — whichever vendor it came from — calls recall and sees that decision. Nothing is re-explained, and no work is paid for twice.
Writes are available to the next agent that reads, immediately. Klio does not push to agents that are already mid-session — an agent sees new state the next time it calls recall.

​
Get started

Quickstart

Connect your first agent to hosted Klio in about two minutes.

The handover loop

The six movements that turn raw activity into something the next agent can actually use.

Tool reference

All ten MCP tools, with their exact parameters and return shapes.

Self-hosting

Run the open-source engine on your own machine or infrastructure.