atlas: Track Coding Agents with Tauri-Based Source Control

Overview

Atlas is a Tauri desktop app for coding-agent source control on macOS and Windows. It links Git commits to the agent sessions that produced them, preserving prompts, tool calls, and changes so teams can understand why code changed rather than relying on commit messages alone. Linux builds are possible, but the project says they are untested.

It runs agents such as Claude Code and Codex alongside its own in-process agent, and can launch other agents through the Agent Client Protocol (ACP). A shared project memory and local context retrieval help agents pick up work across sessions. Atlas is aimed at developers who use multiple coding agents and want their activity, project context, and Git history in one desktop workspace.

Key Features

• Links agent sessions to commits, including commits made outside Atlas, and reconciles links across rebases and amends.
• Captures prompts, messages, tool calls, touched files, and patches in a local session database, with secrets scrubbed before persistence.
• Runs multiple agents in parallel, including Claude Code, Codex, Atlas's native agent, and agents from the ACP registry.
• Shares project memory and context across agents, including plans, decisions, notes, and existing CLAUDE.md and AGENTS.md files.
• Resolves @ mentions for project files, notes, commits, branches, skills, papers, and past sessions.
• Includes project tools such as a Git interface, editor, terminal, markdown knowledge base, research browser, and activity log.
• Works locally without an account or network connection; organization sync is available as an opt-in.

Use Cases

• A developer switches between Claude Code and Codex and wants each agent to inherit useful project context from the other.
• A team needs to investigate why an agent made a change by tracing a commit back to the originating session.
• A developer runs several agents against one codebase and wants to monitor their sessions and Git changes in one workspace.
• A privacy-conscious developer wants local session capture and project memory without uploading code or prompts to run agents.

Getting Started

Download a macOS .dmg or Windows .msi from the Atlas website or the GitHub releases page. To build from source, install Bun and Rust, then run:

bun install
bun run dev:app

See the README for platform prerequisites, build commands, and setup details.

Alternatives

• orca: Orca isolates agents in Git worktrees and supports remote monitoring over SSH, while Atlas links agent activity to commits, prompts, and tool calls.
• claude-code-by-agents: claude-code-by-agents coordinates agents in threaded rooms across local and remote machines, rather than centering on commit-linked agent activity.
• codeg: Codeg organizes agent sessions, code changes, and tasks through ACP across desktop, server, Docker, and mobile, while Atlas focuses on desktop use and Git-linked activity.
• agent-orchestrator: Orchestrator.inc focuses on planning work in isolated branches and tracking pull requests, CI, and reviews in a Kanban.

Considerations

Atlas is still in alpha, though it is changing quickly, with recent commits and frequent releases. The project has 47 contributors, and contributions are not concentrated in one person. The README describes Linux builds as untested, while macOS 13+ and Windows 10+ (x64) are the supported platforms. Building from source requires Bun and Rust, in addition to platform-specific toolchains. Anonymous usage analytics are enabled by default; the project documents what they collect and how to disable them. The project is licensed under Apache-2.0.