Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.225 ·

Auto mode denies safeguard-refused classifier calls without recording a verdict

A safety refusal during auto mode denies the action but no longer counts against your denial limit.

You'll notice New Features
JSON All of v2.1.225
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
PermissionsArea: what it touches
New FeaturesKind: in v2.1.225,
New FeaturesSection of the release
What

When the auto-mode classifier call returns stop_reason "refusal", the action is denied but the denial is no longer treated as a normal block or counted against you.

Details
  • The decision is marked noVerdict: !0 and returns a message explaining the refusal reacts to earlier conversation content rather than the action itself: "Retrying it will hit the same refusal, so don't rewrite or rework the action to get around this".
  • The denial is exempt from the denial counter.
  • In headless mode it instead throws "Agent aborted: auto mode classifier request refused by the safety safeguard in headless mode".
  • Downstream, decisions carrying noVerdict suppress the auto-mode meta message and the config-reject bookkeeping path.
  • Telemetry gains failureKind: "policy_refusal", stopReason, stage1VerdictStands and refusedBySafeguard.
Evidence

Auto mode classifier request refused by the safety safeguard, denying (exempt from the denial counter)

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.225 →

Feedback