Atlas keeps AI edits safe by gating every tool call against allow, ask, and deny rules before it runs. Each file edit computes a unified diff you approve before anything is written, and changes are snapshotted as git patches so they can be rolled back. In 2026 that means automated work stays auditable and under your control.
Permission modes
Before any tool runs, Atlas evaluates it against your rules and resolves to allow, ask, or deny. Unmatched actions default to ask, so nothing surprising runs without a prompt.
This permission model applies to every tool call, from editing a file to running a shell command. You can broaden rules for trusted actions and tighten them for risky ones, keeping a clear boundary around what the agent may do automatically versus what needs your confirmation.
Plan before edits
Atlas drafts a plan in a read-only plan agent and asks before switching to a build agent to implement. You see the shape of a change before it touches your tree.
Separating planning from editing means you can refine the approach while no files are at risk. Once you approve, Atlas implements the plan, and each edit still passes through the diff-and-permission step. Planning and permissions reinforce each other.
Diffs and rollback
Each file edit computes a unified diff that is surfaced for approval before writing. Atlas also snapshots changes as git patches, so a change can be diffed and rolled back.
Reviewing a real diff before it lands is the core safety primitive: you approve exactly what changes. If something is wrong after the fact, the snapshot lets you restore. Together, permissions, plans, diffs, and snapshots make automated edits auditable end to end.
Frequently asked questions
- How does Atlas keep AI edits safe?
- Every tool call is permission-gated against allow, ask, and deny rules, and every edit is shown as a unified diff before it is written.
- Can I control what the agent runs automatically?
- Yes. You set rules that resolve each action to allow, ask, or deny; unmatched actions default to ask.
- Does Atlas plan before editing?
- Yes. Atlas drafts a plan in a read-only plan agent and asks before switching to a build agent to implement.
- Can I undo an Atlas change?
- Yes. Atlas snapshots file changes as git patches, so edits can be diffed and rolled back.
Try Atlas in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install AtlasRelated guides
Atlas with Qwen3 32B (Ollama): dense reasoning over raw speed in 2026
Qwen3 32B (Ollama) in Atlas: dense 20GB weights on a 24GB card, 40K tokens (40,960) of context, Free (self-hosted). Slower than the MoE, steadier on hard problems.
Atlas for Next.js in 2026
Adopt Atlas, the terminal-native AI coding agent, for Next.js development in 2026. Enhance productivity across App Router, server components, and API routes with secure, reviewable AI assistance.
Atlas with Magistral Medium: Multi-Hop Root-Cause Debugging in 2026
Magistral Medium reasons across a 128,000 token window at $2.00 / 1M input tokens and $5.00 / 1M output tokens. Atlas setup, the 16,384 token output cap, tradeoffs.
Atlas with GLM-5.2: A 1M Token Open-Weights Model at $1.40 per Mtok (2026)
GLM-5.2 drives Atlas on a 1M token context at $1.40 / $4.40 per Mtok. Z.ai's June 2026 flagship, the first GLM to reach 1M, with open-weights lineage.
Atlas with Mistral NeMo 12B (Ollama): 128K Context on a 12GB Card in 2026
Run Atlas on Mistral NeMo 12B (Ollama): 7.1GB, a 128K practical context, free self-hosted. Why the Ollama tag says 1000K, and what limit.context to actually set.
Atlas with North Mini Code in 2026: A 64,000 Token Output Budget
North Mini Code gives Atlas a 256,000 token context and a 64,000 token output, 8x Command A's 8,000, listed at $0 per Mtok on both input and output in the registry.
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 GLM-5.1: Reasoning, Cost, and Context in 2026
GLM-5.1 from Z.ai drives Atlas with a 200,000 token context at $1.40 per Mtok input and $4.40 per Mtok output. Setup, honest tradeoffs, and how it compares to GLM-5.2.