Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.225 Home All releases ←olderv2.1.224 v2.1.226newer→
Claude Code v2.1.225

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

You'll notice
Useful3 Signal0
Permissions

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

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 →