Atlas.

Source control for coding agents

The commit remembers
the conversation.

Every agent run produces checkpoints, so a commit stays linked to the prompts, tool calls and file changes that produced it.

macOS is the supported platform; Linux and Windows build from the same Tauri codebase but are untested. Code, notes and sessions stay on your machine unless you sign in to sync.

checkpoint / session

Illustrative
a41f9c2

Rework retry handling in the sync worker

Committed during an agent session

The record exists whether or not it is open

Names and turns above are illustrative, not a captured session. The point is where they live: attached to the commit, still queryable months later.

What survives the scrollback

Run agents side by side

Claude Code, Codex, Atlas's own agent and the wider ACP registry, against the same codebase.

One shared memory

Plans, file changes and failures carry across, so switching agents mid task does not restart the work.

Your notes are context

Markdown in the project, plus the CLAUDE.md and AGENTS.md you already wrote, feed every agent.