Atlas snapshots file changes as git patches while a session runs, each recording a hash and the list of files it touched. That means an edit an agent made 20 turns ago can still be diffed and rolled back, without relying on editor undo history that a background formatter or a second tool may already have overwritten.
Why editor undo is not enough
Undo history is per-editor, per-buffer, and lost on restart. An agent that edits 12 files in a session writes most of them outside any buffer you have open, so there is often nothing to undo in the place you would think to look.
The failure is quiet and arrives late. You notice something wrong an hour later, reach for undo, and find the history is gone or applies to the wrong file. A checkpoint recorded at edit time does not have that problem, because it was written by the thing doing the editing rather than by the thing displaying it.
What a checkpoint records
Each Atlas snapshot stores 2 things: a hash identifying the state and the list of files that changed. Patches are the same format git already speaks, so restoring is a patch application rather than a bespoke file-copy scheme.
Using patches instead of full copies keeps the record small and makes it inspectable with tools you already have. It also means a checkpoint composes with the rest of your git workflow rather than fighting it, which matters when a session's work eventually has to become a commit.
Where rollback sits among the other safeguards
Checkpointing is the 3rd safeguard, not the first. A read-only plan agent catches the wrong approach, per-edit diff review catches the wrong lines, and snapshots catch what both let through and you only recognized later.
Each layer handles a failure the others cannot. Planning cannot know how an edit will actually be written, diff review cannot know how a change will behave once the whole session lands, and rollback cannot prevent anything. Keeping all three is what makes an agent's changes reversible rather than merely visible.
Frequently asked questions
- How do I undo changes an AI coding agent made?
- Atlas snapshots file changes as git patches during a session, so an edit can be diffed and rolled back after it was written.
- Does rollback depend on my editor's undo history?
- No. Checkpoints are written by Atlas at edit time and survive editor restarts, including for files you never had open.
- What does a checkpoint actually store?
- A hash identifying the state and the list of files that changed, recorded as a git patch.
- Do checkpoints leave my machine?
- No. Snapshots are stored locally alongside the repository they describe.
Try Atlas in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install AtlasRelated guides
Atlas with Claude Opus 4.8: The 2026 Model Guide
Claude Opus 4.8 in Atlas: a 1M token context window at $5 / $25 per Mtok with 128K output. When to pin Anthropic's top coding model in 2026, and when not to.
Atlas with GPT-OSS 20B (hosted): the cheap slot that can still think in 2026
Run Atlas on GPT-OSS 20B (hosted) in 2026: $0.03/$0.14 per Mtok on DeepInfra, a 131,072 token context, reasoning on, and $0.00/$0.00 locally in LM Studio.
Atlas for C++ in 2026
In 2026, C++ developers adopt Atlas, the terminal-native AI coding agent, to enhance productivity. Atlas offers secure, context-aware assistance for modern C++ projects, integrating with CMake and ensuring code quality
Atlas with IBM Granite 4.1 8B in 2026
IBM Granite 4.1 8B in Atlas, 2026: a dense 8B model at $0.05/$0.10 per Mtok with a 131,072 token context where max output equals the full window.
Atlas with Kimi K2 Turbo: Pricing, Context, and Setup in 2026
Kimi K2 Turbo in Atlas costs $2.40 per Mtok input and $10.00 per Mtok output on a 256K tokens (262,144) window. A latency purchase, not a capability upgrade.
Atlas with Gemma 2 27B (Ollama): the Free Local Diff Reviewer in 2026
Gemma 2 27B (Ollama) is Google's 2024 flagship open model, 16GB and Free (self-hosted), with 8K tokens (8,192) of context. Use it to review Atlas diffs, not write them.
Atlas with Qwen3 14B (Ollama): the local planning model for 2026
Qwen3 14B (Ollama) in Atlas: dense 9.3GB weights, roughly 11GB to serve, 40K tokens (40,960) of context, Free (self-hosted), better at architecture than raw diffs.
Atlas vs Gemini CLI: A Developer's Guide to Terminal AI Agents in 2026
Atlas vs Gemini CLI in 2026: Compare terminal AI coding agents. Atlas offers permission-gated tool calls and diff-based approvals. Gemini CLI provides a million-plus token context and a free tier.