Morning Edition · Monday, August 10, 2026Published at 2:21 AM EDT · New York
The company says its own controlled test found human reviewers caught a planted dangerous command 13.6 percent of the time, against 89 percent for the automated checker.

Anthropic will make auto mode the default setting in Claude Code for Pro, Max and Team subscribers starting August 14, the company said. In that mode the coding agent stops asking for step-by-step approval and proceeds on its own unless an action is judged irreversible, destructive, or directed outside the user's environment. Enterprise customers, the application programming interface (API) and the cloud platform deployments keep the current behavior for now, with a default rollout there planned within about a month, TechCrunch reported.
The justification is an argument about human attention rather than about model capability. Anthropic says users approve roughly 97 percent of permission prompts. In a controlled test with paid users, reviewers noticed a deliberately planted dangerous command 13.6 percent of the time, while the automated policy checker flagged it 89 percent of the time. Independent developer Simon Willison flagged the change as it went out.
Those numbers come from the vendor and have not been reproduced outside Anthropic. The result is also narrower than it sounds: it measures detection of an injected malicious command inside a controlled task, not the broader class of quiet errors an unsupervised agent can commit across a repository. What is verified is the policy change and its date. What is asserted is that the automated gate is a strict improvement on the human one.
The direction of travel is clear either way. The industry's most widely used coding agent is moving its default from ask-first to act-first, and the safety case rests on a classifier rather than on a person.
Anthropic, which converts approval friction into longer uninterrupted sessions and higher token consumption per user, and the security vendors now selling controls for a default that assumes the agent proceeds.
Part of a tracked trend
Agentic AI Moves Into Enterprise and Government Workflows
Over the next 3-9 months, AI agents move from demos into real enterprise and public-sector workflows, with deployment success tied to domain and task understanding more than raw model capability.
Start a discussion in Townsquare.
More from this edition
The August 14 policy change is confirmed by outside reporting including TechCrunch and 9to5Mac, but the 89 percent versus 13.6 percent comparison rests entirely on Anthropic's own test of 1,053 paid users detecting one planted command, and the classifier's own 11 percent miss rate is the number the framing leaves in the background.
An open-source-intelligence read of how likely this story is true with its real nuance, not a judgment of any outlet. It assesses the claim, weighing independent and adversarial reporting. How we label confidence.
What this means
The gate on agent autonomy is moving from user consent to vendor policy, which shifts the failure mode from "developer approves something careless" to "vendor classifier misjudges something." Anthropic gains throughput and user retention, since agents that run uninterrupted complete longer tasks and use more tokens per session, which supports Claude Code revenue. The exposure sits with teams whose repositories, credentials and cloud accounts are reachable from a developer laptop, and with security vendors now selling controls for a workflow whose default assumption has changed. Enterprise buyers who are already slower to adopt get a delayed rollout, which shows where Anthropic expects the procurement resistance.
What to watch
Observations to monitor, not financial advice.
Synthesized from: Anthropic (Claude blog) · TechCrunch
Comments
1Aug 10, 2:01 PM · edited
Replacing human review with a fixed classifier trades unpredictability for a scoreable adversarial target; red teamers can optimize against the 89 percent checker in ways they cannot against a varied reviewer pool.