Source control for agents. Use multiple coding agents, track their changes and query them in one place

Atlas is source control for coding agents. Every agent run produces checkpoints: commits are linked back to the session that made it alongside the prompts, tool calls, and reasoning. You see which agent did exactly what and why.

Run Claude Code, Codex, Atlas's own agent, or anything from the ACP registry side by side against the same codebase, with shared memory so switching agents mid-task doesn't mean starting over.

• Every commit, explained. A checkpoint links a commit back to the session that produced it: prompts, tool calls, and file changes kept together, queryable months later.
• Run any agent, side by side. Claude Code, Codex, Atlas's own agent, and the wider ACP registry, all in the same window, against the same codebase. Switching agents mid-task doesn't mean starting over.
• One memory, every agent. A decision Claude Code made shows up in Codex's next prompt. Plans, file changes, failures, and architecture notes are shared automatically, matched on-device against what you're asking about.
• Your notes are agent context. Markdown in .atlas/knowledge/, plus the CLAUDE.md and AGENTS.md you already wrote, feed every agent in the project.
• @ anything into a prompt. Files, folders, symbols, branches, commits, notes, papers, and past sessions resolve locally before the prompt is sent.
• Local by default. Code, notes, and sessions stay on your machine. Sign in and create an organisation when you want to sync across a team.

Join the Discord · #general chat · #dev build questions · #feature-requests ideas · #bugs report breakage

Start with CONTRIBUTING.md to send a change, or open an issue for anything you hit.

• Why Atlas
• How it works
• Checkpoints
• Features
• Download
• Build from source
• Contributing
• Local by default
• Links

Agents now write a large share of the code and keep none of the reasoning behind it. Atlas records both, and makes them queryable: what changed, by whose agent, at what point in time.

• Agents start from zero every session. Atlas keeps a persistent on-device memory of decisions, plans, and changes, and pushes the relevant parts into every turn.
• Switching agents loses the thread. The first message of a new session carries a curated fact pack and the tail of your last one, even when that session ran on a different agent.
• You can't review what you can't see. Every session is stored and searchable, next to a real commit graph and file-level diffs of what actually landed.
• Context lives in ten places. The knowledge base, CLAUDE.md, AGENTS.md, Claude Code's memory files, and Codex's history fold into one index every agent reads from.
• Nothing is locked in. Notes are markdown, canvases are JSON, sessions are JSONL, and the editor is a file on disk. Close Atlas and pick up in vim. The one exception is the checkpoint record (which agent session produced which commit), which is SQLite in the project's gitignored .atlas/, because it is queried, not read.
• Built for agents from the ground up. The agent runtime, shared memory, and session history are the foundation the rest of the app is built on.

Atlas runs your agents as they are, and enriches what they see.

Claude Code and Codex run as external subprocesses over ACP, the most-used, most-tested path. The Atlas agent runs in-process on Cersei, our Rust agent framework.

Beyond those, Atlas can spawn any agent in the ACP registry (Cursor, OpenCode, Kilo Code, and more), pulling in each one's official binary automatically. All of them go through the same send path, so everything below applies whichever one you pick.

Before your message reaches the agent, Atlas assembles context around it:

• One path, no per-agent special-casing. Run your existing Claude Code or Codex subscription through Atlas and the session gets more context, with no change to how you work.
• Claude Code's memory is visible to Codex, and the reverse. Neither agent can read the other's history on its own.
• Folders resolve to a pointer, not a paste. @-ing a 5000-line file sends a path the agent reads on demand, so one mention doesn't occupy the context window for the rest of the session.
• Embedding runs on your machine. Retrieval never leaves the device.

A checkpoint is what a commit doesn't tell you on its own: which session produced it, what the agent was asked, the tool calls it made, and the reasoning behind the change, kept together instead of lost the moment the terminal scrolls.

Atlas records every agent session locally in .atlas/sessions.db, with secrets scrubbed before anything touches disk. When you commit (from any tool, even with Atlas closed), the commit is linked back to the session that produced it as a checkpoint, and links survive rebases and amends.

You don't have to read the raw transcript to get the context back: select a checkpoint and chat with it directly, and it answers from what actually happened in that session. Local mode works fully offline with no account.

Works with no account and no network.

Grab the latest .dmg from tryatlas.cc or the releases page.

To use the Claude Code agent, install the claude CLI and put it on your PATH. Atlas's native agent needs no external CLI.

Requires Bun, Rust (stable, via rustup), and Xcode Command Line Tools.

git clone https://github.com/pacifio/atlas
cd atlas
bun install
bun run dev:app

The first Rust compile takes a few minutes; after that it is seconds. Use bun run dev for frontend-only iteration, though anything calling invoke() needs dev:app.

Production builds:

bun run build:app       # .app bundle
bun run build:app:dmg   # .app + .dmg installer

See CONTRIBUTING.md. One thing catches people out:

• Feature work targets the current version branch, not main. main only receives a finished version branch, and that merge is the release.

ARCHITECTURE.md covers how Atlas is built. SECURITY.md covers reporting vulnerabilities.

• Your code, notes, and sessions stay on your machine. Nothing is uploaded to run an agent.
• Secrets are scrubbed before anything is written to disk. Not before upload, before persistence.
• Session capture is local-only by default. The Checkpoints record of your agent sessions is written to .atlas/sessions.db on your machine and stays there. No account required, and nothing sent anywhere until you explicitly opt in to sync.
• Accounts are opt-in. Sign in to create an organisation and sync across devices and teammates.
• Anonymous usage analytics are on by default. Coarse metadata, never code or prompts. What's collected, and how to turn it off.

• Website: tryatlas.cc
• Docs: docs.tryatlas.cc
• Discord: discord.gg/GmnFggaPfP
• Issues: github.com/pacifio/atlas/issues
• Telemetry: what Atlas collects, and how to turn it off

MIT. See LICENSE.