LibreAI / Dev Tools / atlas
// devtools · pacifio/atlas

atlas

Source control for agents — run coding agents side by side, track changes and query their history.

★ 9.4k stars⑂ 366 forksApache-2.0updated 2026-10
▦ visual — this project's README ships no embeddable screenshot,
so here's a placeholder. The guide below is complete regardless.
// project facts

Project facts

atlas is an open-source dev tools project by pacifio (pacifio/atlas on GitHub). It has 9,429 GitHub stars and 366 forks, is released under the Apache-2.0 license, and was last updated on GitHub on 8 October 2026.

Repository
pacifio/atlas
GitHub stars
9,429
Forks
366
License
Apache-2.0
Last updated on GitHub
8 October 2026
Category
Dev Tools
Listing
Full install guide
Official site
Official site
// how it works

How it works

  1. Clarify your goal

    Decide which coding agents you will run through Atlas and which project to open first; Atlas uses your existing agent subscriptions and CLIs.

  2. Get the project

    Clone pacifio/atlas from GitHub (or use the install path in the run steps below) and skim its README for the parts relevant to your goal.

  3. Install and configure

    Download the macOS .dmg or Windows .msi from the site or releases page, or build from source with Bun and Rust; install the claude CLI if you want the Claude Code agent.

  4. Run your first task

    Open a project, run a task with one agent, make a commit, then open the checkpoint to see the prompts, tool calls and file changes linked to it.

// features

Why people love it

Checkpoints that explain commits

Every commit links back to the session that produced it — prompts, tool calls and file changes kept together and queryable months later.

Multiple agents, one window

Run Claude Code, Codex, Atlas's own agent and other ACP-registry agents side by side on the same codebase, switching mid-task without starting over.

One shared memory

Plans, file changes, failures and architecture notes are shared automatically across agents, matched on-device against what you ask.

Your notes are context

Markdown in .atlas/knowledge/, plus your existing CLAUDE.md and AGENTS.md, feeds every agent in the project.

@-mention anything

Files, folders, symbols, branches, commits, notes, papers and past sessions resolve locally into a prompt — folders resolve to a pointer, not a paste.

Local by default

Code, notes and sessions stay on your machine, with on-device embedding; sign in and create an organisation only when you want team sync.

Advertisement
// run it

Run it yourself

  1. Clone the repository

    Get the source from the official GitHub repository for atlas.

    git clone https://github.com/pacifio/atlas.git
    cd atlas
  2. Install Atlas

    Download the latest build for macOS or Windows from the official site or the GitHub releases page, as the README's Download section directs.

    # Download the .dmg (macOS) or .msi (Windows) from https://www.tryatlas.cc/ or the releases page — see README
  3. Or build from source

    With Bun and Rust (stable, via rustup) installed, build the Tauri app from the cloned repo per the README's build section.

    bun install  # then follow the README 'Build from source' steps for your platform
// use cases

What you can build

Advertisement
// faq

Questions, answered

Who maintains atlas?

pacifio, through the pacifio/atlas repository, with the product site at tryatlas.cc.

Is atlas free to use?

Yes — the project is open source under the Apache-2.0 license as recorded for this listing. See the license terms for any conditions on redistribution.

Does atlas need a paid API key?

Atlas itself is free and open source; the agents you run through it use your existing subscriptions or CLIs, such as your Claude Code setup.

How does Atlas compare to using each coding agent in its own terminal?

Separate terminals give each agent amnesia — histories are invisible to each other and commits carry no provenance. Atlas shares memory across agents and records checkpoints that tie commits to sessions, while staying local by default.

How do I get started with atlas?

Clone the repository (or use the documented installer), follow the install and configure steps on this page, and run the smallest real task first — open a project, run a task with one agent, make a commit, then open the checkpoint to see the prompts, tool calls and file changes linked to it.

// keep exploring

Similar tools

Dev Tools

vibe-kanban

A kanban board for coding agents — plan tasks, run Claude Code or Codex in parallel, review diffs

★ 28.3k starsApache-2.0
View guide →
Dev Tools

mission-control

Self-hosted control plane for AI agents: dispatch tasks, review runs, track spend, and operate OpenClaw, Claude Code, Codex, and other runtimes.

★ 6.3k starsMIT
View guide →
Dev Tools

agentacct

See what your coding agents did — and what each task cost in tokens.

★ 763 starsMIT
View guide →
Dev Tools

project-codeguard

Open-source security framework for AI coding agents — secure by default.

★ 348 starsCustom
View guide →
Dev Tools

context-mode

Context optimization for coding agents: sandbox tool output, keep sessions lean, remember more

★ 25.7k starsElastic License 2.0
View guide →
Dev Tools

motion-skills

50 open-source skills that teach AI coding agents to make motion graphics.

★ 689 starsMIT
View guide →
// alternatives

Alternatives in Dev Tools

The most-starred other Dev Tools projects in the LibreAI catalogue — the realistic shortlist if atlas is not the right fit.

Get atlas

Free and open — grab the source, star the repo, and start creating.