Atlas · agents
Sandboxing
A wall the operating system puts around what an agent's commands can touch, stronger than any instruction in a prompt.
See it working: Plate II
In plain words
Telling an agent not to touch a folder is a request. A sandbox is a wall: the operating system itself refuses.
How it works
Claude Code’s Bash sandbox is enforced by the operating system around shell commands. It covers the shell, not every tool in the harness, so permission rules still matter. Those rules are checked in deny, ask, allow order.
Going deeper
Plate II simulates a hook rejecting a deploy. That is enforcement by the harness, a different layer from the operating system’s sandbox.
Sources
- Sandboxing Anthropic
The Bash sandbox is a boundary that the operating system enforces
- Configure permissions Anthropic
Rules are evaluated in order: deny, then ask, then allow.
- Hooks reference Anthropic
Before a tool call executes. Can block it
blocks the tool call, and shows Claude the reason.
Quotes were checked against the live pages on 2026-11-08.