pacifio/atlas

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

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 15th, 2026
Created on May 14th, 2026
Open Issues & Pull Requests: 21 (+0)
GitHub issues: Enabled
Number of forks: 282
Total Stargazers: 4,729 (+1)
Total Subscribers: 24 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.8 days
Mean response time: 14.2 days
90th percentile: 37.6 days
Tracked items: 64

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 11% of issues opened in the past year have never received a reply. 82% of issues opened in the past year have been closed, leaving a working backlog. Three people close 97% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 3
Closed in 7 days: 5
Avg open age: 37 days
Stale 30+ days: 2
Stale 90+ days: 0

Recent activity

Opened in 7 days: 3
Closed in 7 days: 5
Comments in 7 days: 2
Events in 7 days: 6

Top labels

  • good first issue (26)
  • enhancement (11)
  • bug (5)
  • dependencies (1)
  • help wanted (1)
  • javascript (1)

Detailed Description

Atlas is source control for coding agents that tracks changes made by multiple AI coding assistants in a unified interface.

The tool addresses the challenge of managing code generated by different AI agents by creating checkpoints for each agent run. These checkpoints link commits back to the session that produced them, preserving the prompts, tool calls, and reasoning alongside file changes. This makes it possible to understand exactly which agent made what changes and why, even months later. The approach allows developers to run multiple agents—Claude Code, Codex, Atlas's own agent, or others from the ACP registry—against the same codebase simultaneously. Agents share memory across sessions, so switching between them mid-task preserves context and prevents starting over.

Atlas suits teams and individual developers working with multiple coding agents who need visibility into agent behavior and want to avoid context loss when switching between tools. The project is designed for those who want agents to build on each other's work through shared memory and queryable session history. It works best for projects where understanding the reasoning behind generated code matters, and where teams need to coordinate multiple agents on the same task. The tool stores code, notes, and sessions locally by default, with optional team synchronization through sign-in and organization features.

Development activity shows consistent engagement with the codebase, regular updates addressing user-reported issues, and active maintenance of the core functionality. The project maintains responsiveness to feature requests and bug reports from its user community.