What is Sofar
A portable, tool-independent record of AI-assisted work — plan, status, and decisions with rationale — that any session, model, or CLI can read and write.
Your agents do the work. Sofar keeps the record — the plan, the progress, and every decision with its why — readable by any tool, any model, any teammate.
git records what the code became. Nothing records what the work was trying to do, how far it got, or why it went the way it did. Sofar is that record.
Mechanics, in four lines
- Files in your repo. The record lives in
.sofar/, versioned in git. No cloud dependency, no per-vendor adapter. - An append-only event log is the truth. Human-readable projections (plan, decisions, status) are generated from it.
- Works beside every tool. Hooks and MCP where a tool supports them (Claude Code); a plain-text convention and CLI everywhere else (OpenCode, Codex, Cursor). Agents read the record first, and write back status and rationale when they stop.
- Never in the control path. Sofar does not run, route, or monitor your agents. A record can only go stale; an orchestrator can break your work.
What Sofar will never do
- Run your agents. Sofar sits beside your tools, never between you and them.
- Watch sessions live. Your agent vendors ship that in-tool; it is not the product.
- Guess your progress. Sessions declare their state; nothing is inferred from commit noise. A confidently wrong 72% is worse than none.
Where to go next
- Quickstart — install the CLI and start the record in one command.
- Telemetry policy — the published, opt-in, metadata-only schema. Content never leaves your repo.
- The format on GitHub — MIT-licensed engine, open spec.