atlas

<div align="center"> <img src="src/assets/atlas-icon.svg" alt="Atlas" width="88" height="88" />

Atlas

Know which prompt shipped which line.

The agentic visibility & control layer your SDLC was missing.

<br />

<a href="https://trendshift.io/repositories/56020?utm_source=repository-badge&amp;utm_medium=badge&amp;utm_campaign=badge-repository-56020" target="_blank" rel="noopener noreferrer"><img src="https://trendshift.io/api/badge/repositories/56020" alt="pacifio%2Fatlas | Trendshift" width="250" height="55"/></a> <a href="https://trendshift.io/repositories/56020?utm_source=trendshift-badge&amp;utm_medium=badge&amp;utm_campaign=badge-trendshift-56020" target="_blank" rel="noopener noreferrer"><img src="https://trendshift.io/api/badge/trendshift/repositories/56020/daily?language=Rust" alt="pacifio%2Fatlas | Trendshift" width="250" height="55"/></a> <a href="https://trendshift.io/repositories/56020?utm_source=trendshift-badge&amp;utm_medium=badge&amp;utm_campaign=badge-trendshift-56020" target="_blank" rel="noopener noreferrer"><img src="https://trendshift.io/api/badge/trendshift/repositories/56020/weekly?language=Rust" alt="pacifio%2Fatlas | Trendshift" width="250" height="55"/></a>

<br />

<a href="https://github.com/pacifio/atlas/stargazers"><img src="https://img.shields.io/github/stars/pacifio/atlas?style=social" alt="GitHub stars"></a> <a href="https://github.com/pacifio/atlas/forks"><img src="https://img.shields.io/github/forks/pacifio/atlas?style=social" alt="GitHub forks"></a> <a href="https://github.com/pacifio/atlas/graphs/contributors"><img src="https://img.shields.io/github/contributors/pacifio/atlas?label=contributors&color=blue" alt="Contributors"></a>

_{Download · Docs · Learn · Website · Contributing · Issues}

<br /> <img src=".github/assets/readme/timeline-comments.webp" alt="The Atlas timeline: a team's agent sessions grouped by day, one session open with its prompt, tool calls and a teammate's comment on a tool call" width="900" /> </div>

Your entire engineering team uses coding agents. You get stacked PRs, you see the diffs without the context. When something breaks in production, do you know whose agent changed it, and what it was told?

That's why we built Atlas: every coding agent your team runs, recorded and linked to the commits it produced, on a shared timeline the whole team can collaborate and comment on.

Desktop app or terminal

Both feed the same team timeline, so mix them: one teammate in the desktop app, another in a terminal over SSH.

Atlas desktop. The control-surface IDE below.

Atlas CLI. Happy in your terminal? atlas-cli hooks into the agents you already run (Claude Code, Codex, Cursor, Copilot, OpenCode, Droid, Antigravity and Pi), records every session, links its commits and gives every agent one shared memory. macOS and Linux.

curl -fsSL https://github.com/tryatlas/cli/releases/latest/download/install.sh | sh

For engineers

Atlas is a "control-surface IDE" built around managing your agents' context.

• Bring every agent, run them in parallel. Claude Code, Codex and more, side by side.
• Teach once, every agent remembers. Shared memory carries a correction you give one agent over to the rest.
• Context follows you between agents. @ a file, repo, branch or past session. Your CLAUDE.md, AGENTS.md and knowledge notes reach every agent, and a new session is briefed on where the last one stopped.
• Conversations are context too. Team chat, shared prompts and Spaces, right next to your agents.
• Steer a live session from anywhere. Start remote control on a desktop session and drive it from a browser, on another computer or your phone. Invite teammates to watch, and hand one of them the controls.
• The rest of the IDE is there too. Editor, block terminal, source control and pull requests, in the same window.

<img src=".github/assets/readme/session.webp" alt="A session in the Atlas desktop app: the agent's answer about the repository's git status, a details panel with the branch, changes, Commit, push &amp; PR, attached projects and Remote control marked Live, and a toast confirming remote control is on" width="900" />

For engineering managers

• Trace every incident to its prompt. See whose agent changed what, and which session caused the break.
• Measure how your team ships with agents. The ROI dashboard sets AI spend against the commits it shipped: cost per commit and per active hour, by project, person and model.
• Step in while the agent works. A live timeline of every agent session, your comments land directly in the developer's running session.
• One organization, every project. Members see each other's sessions on the timeline and comment on each other's work, from the desktop app or the web app.

<img src=".github/assets/readme/usage.webp" alt="Usage in the desktop app: tokens, estimated cost, sessions, messages and cache hit rate for 30 days, tokens by day, token efficiency, and a table of sessions by agent and model" width="900" />

Multiplayer

An organization has members and projects (think git repo). Put a project's sessions in the cloud and every teammate who opens the same repository adds their sessions to it.

• One timeline for the whole team. Every member's sessions, both live and finished, with agent, model, tokens, and the checkpoints that tie each one to its commits. Filter by project, agent or person.
• Comment on each other's sessions. Anchor a thread to a whole session or to one prompt, response, tool call or checkpoint. @-mention, reply, resolve. On a live session, the comment lands in the developer's session while the agent is still working.
• Talk next to the work. Channels and DMs where a message carries a session or checkpoint card, plus calls, prompt drafts you write together, and Spaces.
• Ask Atlas about the team. "What did we work on today?" Atlas, your organization's own agent, answers from everyone's sessions, and can run Deep research or post to a channel when you ask.

Only the record of agent work syncs, never your source tree, and secrets are redacted on your machine first. What syncs, exactly →

<table> <tr> <td width="50%" valign="top"><img src=".github/assets/readme/team-chat.webp" alt="Team chat in the desktop app: the #general channel with a recorded session card and a session digest of the day's work" /></td> <td width="50%" valign="top"><img src=".github/assets/readme/ask-atlas.webp" alt="Ask Atlas in the desktop app: an answer listing the day's sessions by teammate, each linked by its session id" /></td> </tr> </table>

Checkpoints

A checkpoint is like a commit++ with more info: 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.

With session capture on (it's off until you turn it on per project), 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.

How it works

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

Claude Code and Codex run as external subprocesses over ACP and get the most support due to their popularity. Atlas Agent (the native one) runs in-process on its own engine.

Atlas can also 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 to whichever one you pick.

[!NOTE] QA on the long tail of registry agents is ongoing.

Atlas never rewrites your prompt. Here is what reaches the agent, and how:

| Context | Where it comes from | How the agent gets it | | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | | @ mentions | Resolved locally in Rust before the prompt is sent. Notes, skills, and past sessions are inlined; files and folders resolve to a path | With your message | | Shared agent memory | Active plan, decisions, file changes, failures, and architecture notes, written by any agent | Through Atlas's on-device memory server, which agents call as a tool | | Session briefing | The tail of the last session in this repository (from any agent), plus the useful parts of CLAUDE.md, AGENTS.md, and Claude's memory files | Read by the agent when a session starts | | Semantic search | An on-device index of your instruction files, agent memory files, and knowledge notes | Searched by the agent through the memory server |

• 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