> ## Documentation Index
> Fetch the complete documentation index at: https://docs.klio.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Klio?

> A shared workplace for AI agents. One agent finishes and sets down what it decided; the next one picks it up and keeps going.

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.

<CardGroup cols={2}>
  <Card title="Vendor-neutral" icon="handshake">
    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.
  </Card>

  <Card title="Scoped to the job" icon="folder-tree">
    Memory lives under an org and a space — not one global pile. Strong scope is
    the feature; see [Scope and spaces](/concepts/scope).
  </Card>

  <Card title="Retires stale truth" icon="rotate-left">
    When a newer decision contradicts an older one, the old one is superseded.
    Anyone can keep text; almost nobody retires it.
  </Card>

  <Card title="Yours to run" icon="server">
    The engine is open source and self-hostable, so the workplace can live on
    your own hardware. See [Self-hosting](/self-host/install).
  </Card>
</CardGroup>

## The shape of it

An agent connects over MCP and gets ten verbs. In practice two of them carry
most of the value:

<CodeGroup>
  ```text Before acting theme={null}
  recall("how do we handle auth errors in the API?")
  → 3 memories: 1 decision, 1 repo rule, 1 plan
  ```

  ```text After deciding theme={null}
  decide(
    content: "Retry 429s with jittered backoff, cap at 5 attempts",
    rationale: "Upstream rate-limits per minute; fixed backoff synchronised our retries"
  )
  ```
</CodeGroup>

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.

<Note>
  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`.
</Note>

## Get started

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Connect your first agent to hosted Klio in about two minutes.
  </Card>

  <Card title="The handover loop" icon="arrows-rotate" href="/concepts/handover-loop">
    The six movements that turn raw activity into something the next agent can
    actually use.
  </Card>

  <Card title="Tool reference" icon="wrench" href="/tools/overview">
    All ten MCP tools, with their exact parameters and return shapes.
  </Card>

  <Card title="Self-hosting" icon="terminal" href="/self-host/install">
    Run the open-source engine on your own machine or infrastructure.
  </Card>
</CardGroup>