Originally published at vinpatel.com
If you run Claude Code without checking your settings this week, auto mode is now the default and it decides what runs without asking you first.
That is not a UI tweak. It is Anthropic changing the default trust level for every developer who opens the tool without reading the changelog.
Claude Code launched in February 2025, and every file edit or shell command needed a manual approval before it ran.
Later in 2025, Anthropic added an auto-approve mode, but it stayed opt-in, tucked inside settings for developers who wanted to skip the confirmation prompts.
This week, Anthropic flipped that switch. Auto mode now ships on by default in Claude Code, and manual approval is the thing you now have to go find and turn back on.
The through-line is simple: Anthropic has spent the past year and a half training developers to trust Claude Code's judgment enough that asking permission for every action became the exception instead of the rule. Each step removed one more prompt between the model deciding something and the model doing it. The default flip is the last step in that sequence, and it means teams who never touched the settings are now running a coding agent that executes first and reports back, not one that waits in line for a yes.
That is a real cost for anyone running Claude Code in a shared repo or a CI pipeline without reviewing what auto mode is allowed to touch. A model that used to pause before running a shell command now runs it, and the developer finds out after. If your workflow depends on that pause — a staging check, a review gate, a second pair of eyes — it disappears the moment you update without checking the settings page.
Expect other agentic coding tools to make the same move. If a major competitor to Claude Code has not shipped autonomous execution as its own default by the end of 2026, that will be the outlier, not Anthropic.
For a closer look at how Claude Code's permission model, skills, and subagents actually work day to day, the daily driver breakdown is worth the read. And if you have been running Claude Code across a few projects lately and noticed anything different, the recent quality reports cover exactly that pattern. Get the next shift like this one before it ships — subscribe at vinpatel.com/subscribe/.
Top comments (1)
Auto mode shifts the trust boundary from the user prompt to the classifier and policy layer. That can be a good UX move, but only if users can understand why an action was allowed, what was blocked, and how to recover when the classifier is wrong.