PSA: Claude Code now enables auto mode as default, Anthropic says

What happened

I'll draft the post from the given facts only and keep the prose within the requested structure and length.Anthropic has changed the default permission setting in Claude Code, according to 9to5Mac. Auto mode is now the default. The change applies starting today. Sessions for Pro, Max, and Team users now open under auto mode unless a user or an administrator has already pinned a different setting. 9to5Mac framed the notice as a PSA, which matches the shape of the change: it is not a new product line and it is not limited to people who go looking for a settings panel. It is a default that attaches to sessions those paid plans start now. The named plans are Pro, Max, and Team. The report does not assign the same default to any other plan, and it does not give a version number or a calendar date beyond starting today.

The mechanics sit in the permission setting that Claude Code applies when a session starts. There is a product default, and there is a pin. Auto mode is the new default. A pin, if one exists, wins. The pin can come from the user who owns the session or from an administrator. That is the entire control surface named in the report: default versus pinned alternative, user pin versus administrator pin. Nothing in the summary says Anthropic removed other permission settings. Nothing says auto mode is now the only available setting. The change is which setting a session inherits when nobody has pinned one. For anyone who already chose a setting and pinned it, the new default is not the effective policy.

The technical detail

The split between user pins and administrator pins is the part that matters in a Team workspace. An individual Pro or Max user who pinned a setting keeps that setting. A Team user who never pinned one now inherits auto mode. A Team administrator who pinned a setting for the workspace keeps that pin in front of the new default. A Team administrator who never pinned one now has auto mode as the workspace’s effective permission posture for new sessions. The report does not describe a third override, a grace period, or a prompt that asks the user to confirm the new default before the first session of the day. The inheritance rule is simple: Pro, Max, and Team sessions use auto mode unless a pin is already in place.

Why it matters for builders

For engineers and builders, the permission setting is the gate between Claude Code proposing work and that work actually running in a real tree. Changing the default does not change the model. It changes what happens when a Pro, Max, or Team user starts a session and has never pinned a preference. People who liked a more restrictive posture because they never touched the setting now have to pin that posture if they still want it. People who already live in auto mode will see no change. People who work on a Team plan need to know whether their administrator pinned something, because the administrator’s pin is part of the same rule. The practical effect is on the next session, not on a marketing page. If you open Claude Code today on Pro, Max, or Team and you have no pin, you are in auto mode.

The market context is that Anthropic is moving a coding-agent default across its paid individual plans and its Team plan at the same time. Defaults are how most users actually experience a product, because most users never pin a setting. Shipping the change as a default, then having 9to5Mac report it as a PSA, is how a permission change reaches people who will not read a changelog before they start a session. The report names Pro, Max, and Team and does not name a broader free tier or a different enterprise SKU. That is the commercial boundary of the announcement as written. Competitors are not named, and no share, pricing, or usage figures are given. The competitive fact that is actually in the report is narrower: Anthropic chose auto mode as the unattended default for those three plans, and it left pinned settings in place so the default is not a hard lock.

Market and competitive context

The takeaway is operational and immediate. Check whether you have a permission setting pinned. If you do, this announcement does not change your sessions. If you do not, and you are on Pro, Max, or Team, sessions starting today use auto mode. Team administrators should treat the absence of a pin as a policy decision they have now made by inaction, because the new default fills that gap. If a workspace wants a setting other than auto mode, someone has to pin it. If a workspace wants auto mode, they do not have to do anything. Do not assume an old implicit default will come back. The only named way to keep a different setting is to pin it, as a user or as an administrator.

What to watch next

The report leaves several gaps that are worth treating as open rather than filling in. It does not define what auto mode is allowed to do, only that it is now the default permission setting. It does not say whether sessions already running are rewritten or only new sessions pick up the default. It does not say what happens on plans other than Pro, Max, and Team. It does not say whether a user pin and an administrator pin can conflict, or which one wins if both exist. Those details are not in the summary, so they are not settled here. The settled facts are only these: Claude Code now defaults to auto mode, the change starts today, it applies to Pro, Max, and Team sessions, and a user or administrator pin is the override.