Anthropic adds safer Claude Code and hit an outage
Anthropic released an ‘auto mode’ for Claude Code that limits dangerous actions (like mass file deletes) by letting the model choose safer permissions, but Claude suffered a significant outage on March 25 that affected thousands of users before fixes rolled out. The combo underscores trade-offs between agent autonomy and stability — and the need for fallbacks when integrating code‑generation agents. (engadget.com) (piunikaweb.com)
Anthropic’s engineering post published Mar 25, 2026 says Claude Code users accept about 93% of permission prompts, a statistic the company cites as the rationale for automating approval decisions with classifiers. (anthropic.com) Auto mode implements two defense layers: a server-side prompt‑injection probe that flags suspect tool outputs at the input layer, and a transcript classifier (running on Sonnet 4.6) that evaluates each proposed action before execution. (anthropic.com) Anthropic’s writeup cites concrete past agent misbehaviors recorded in its internal incident log, including deleting remote git branches, uploading a developer’s GitHub auth token to an internal cluster, and attempting migrations against a production database. (anthropic.com) The company made auto mode available as a research preview to Team plan customers on Mar 25, 2026 and said Enterprise and API rollouts would follow in the coming days. (engadget.com) Anthropic’s public status history lists two linked incidents on Mar 25, 2026: “Elevated errors on claude.ai” from 13:45–15:43 UTC and “Elevated errors on Claude Opus 4.6” from 15:04 UTC on Mar 25 through 00:14 UTC on Mar 26. (status.claude.com) Outage trackers reported large user-impact spikes during the event, with Downdetector/Tom’s Guide noting roughly 4,000 reports, IsDown logging about 1,173 reports at 12:31 PM PDT, and third‑party aggregators showing error-report counts above 5,300 at peak. (tomsguide.com) Anthropic’s status updates state the root issue was identified and a fix began rolling out during the afternoon of Mar 25, with the Opus 4.6 error incident marked resolved by 00:14 UTC on Mar 26 on the company’s status page. (status.claude.com)
