Rethinking Claude Code Best Practices — Lydia Hallie, Anthropic
Anthropic’s Claude Code talk shifts best practices toward sandboxed execution and enforced verification as agents run longer and with less direct supervision.
The talk describes longer-running Claude Code sessions, with auto mode handling some approvals and sandboxes limiting shell-command access. In a cited study, auto mode blocked **89%** of dangerous commands, while people caught **about 14%**.
If you run coding agents unattended, define what commands can reach, isolate sessions where possible, and make tests or other checks gate completion. The speaker also recommends trimming setup instructions that newer models no longer need and using hooks for checks that must run.
The talk describes longer-running Claude Code sessions, with auto mode handling some approvals and sandboxes limiting shell-command access. In a cited study, auto mode blocked **89%** of dangerous commands, while people caught **about 14%**. If you run coding agents unattended, define what commands can reach, isolate sessions where possible, and make tests or other checks gate completion. The speaker also recommends trimming setup instructions that newer models no longer need and using hooks for checks that must run. Auto mode still let roughly **one in ten** dangerous commands through in that study. Sandboxing covered shell commands and their child processes, but not Claude’s own files, MCP servers, or hooks; verification quality still depends on the checks you configure.
This frames unattended coding-agent safety as layered containment and verification, not as approval automation alone. The reported auto-mode block rate leaves residual risk, and the stated sandbox boundaries exclude files, MCP servers, and hooks, so those paths need separate controls.