Home

Logos

When one coding agent stops, the next one continues the work.

Logos is a local-first memory and continuity layer for coding agents. Claude Code, Cursor, Codex and your own agents share one vault over MCP. An agent checkpoints what it did, and the next one resumes exactly where it stopped. The next one can be a different model, in a different tool, on a different day.

Claude Code  ──▶  checkpoint  ──▶  Logos  ──▶  resume  ──▶  Cursor
                                (your vault)

It runs on your machine, against a folder of markdown files you own, and uploads nothing. The SQLite index in .logos/ is a cache: delete it, run logos index, and you lose nothing.

Start here

If you want to…	Read
Install it and connect your agents	Installation
See the whole loop in five minutes	Quick Start
Understand checkpoints, memories, projects and the vault	Core Concepts
Know how an agent should use it, step by step	The Handoff Loop
Know which editors and agents work, and how to wire one by hand	Agent Hosts
Look up an MCP tool	MCP Tools Reference
Look up a command	CLI Reference
Manage what it remembers about you	Memory
Bring in history you already have	Importing History
Control what it does on its own, and what it records	Settings and Privacy
Open the vault in Obsidian, or share it with a team	The Vault
Use the engine from your own Go agent	Embedding in Go
Fix something	Troubleshooting

The idea in one paragraph

Anyone can restate a goal. The expensive knowledge is what was already tried and didn't work, and that is exactly what dies with a session. Logos keeps it. Every checkpoint separates verified (what was actually run and seen) from failed (what was ruled out, and why). before_you_try puts those dead ends in front of the next agent before it proposes the same thing again.

Three promises

1. The vault is the truth. Everything durable is markdown. The index is rebuildable.
2. Nothing leaves the machine. No telemetry. The only network calls are to a local model runtime you configured and, when you type logos update, GitHub. logos doctor --egress lists every address.
3. Every feature announces itself. When Logos restores, skips or repairs something, it says so, with the number.

---

Logos was developed under the name brain. If you have a 0.4 vault in ~/brain, see Troubleshooting → Moving from brain.