tj retweeted
Atlas by @adib_builds is a 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.
He’s fully onboard and will claim and join comms
Ca;FLAKs6BYszqb6qv5AQ16zPQnHHT5TLmY5df7pLVpump
we got an AI grant through OpenAI’s startup program.
now we’re giving builders a chance to put @tryatlas_cc to work.
testing solo? bringing your team?
we have special coupon codes for free access and AI credits.
run your coding agents. keep the history behind their changes.
your agents can write the code.
but can you track which one changed what and why?
