Skip to main content
A shared text store is not a workplace. The difference is what happens between one agent writing and the next one reading — six movements, of which the last three are the ones a plain database will not do for you.

Clock in

An agent connects over MCP and is resolved to an org, an agent identity, and optionally a space. No vendor owns the door — Claude Code, Cursor, Codex and your own agents all arrive the same way.

Capture

Work is recorded as it happens through remember, decide, plan, observe, and note. Secrets and personal data are stripped before anything is persisted, and that step fails closed.

File to the job

Every write lands under an org, and optionally a space. The job’s knowledge stays with the job rather than in one undifferentiated pile. See Scope and spaces.

Distil

Raw activity is condensed into the few durable facts worth keeping. The next agent should inherit conclusions, not transcripts — a thousand observations are worth less than the one decision they led to.

Retire

When a newer memory contradicts an older one, the old one is superseded rather than left to compete with it. This is the step almost nothing else does, and it is why recall stays sharp instead of degrading into a pile of mutually contradictory notes.

Hand over

The next agent calls recall and receives current state. One writes; the next to look already sees it.

​
Why distil and retire matter

Keeping text is easy. Two things make stored context stop being useful over time, and both are the store’s job to handle:
An agent that logs every step produces thousands of low-value entries. Recall over that returns noise, and the model spends its context budget reading things that did not matter. Distilling means a session’s worth of activity collapses into the handful of facts that survive it.
Six months in, the store holds “we use fixed backoff” and “we use jittered backoff.” Both surface. The agent picks one — sometimes the wrong one — and quietly undoes work. Superseding means the retired statement stops being returned, so nobody acts on stale truth.

​
What the loop does not do

Klio does not notify running agents. A write is available to the next agent that reads, immediately — but an agent already mid-session will not learn about it until it calls recall again. If you need two agents to coordinate within a single turn, that is a job for your orchestration layer, not for memory.
Nor does it decide what is worth keeping on your behalf. Agents write what they are told to write. The prompt guidance in the Quickstart exists because a workplace where nobody writes anything down is just an empty room.