Cross-tool continuity

Without Klio

Each coding tool keeps its own context. Decide something in Cursor, open Claude Code, and you are explaining it again — or worse, the second tool quietly contradicts the first.

With Klio in the loop

1. 1

   You settle a question in one tool, and its agent sets the decision down in Klio.

2. 2

   You open a different tool on the same project.

3. 3

   Its agent recalls the project before acting and starts from what was already decided.

The call an agent makes

decide(
  {
    "content": "API errors return RFC 7807 problem+json, not ad-hoc shapes.",
    "rationale": "Three handlers already do this; the rest should match."
  }
)

Real tool, illustrative payload. The full contract for every tool is in the docs.

What changes

Your tools stop being silos. The decision travels with the project, not with the window you happened to make it in.