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

Claude Code v2.1.225 ·

Auto-mode classifier failures are distinguished from classifier denials

When the auto-mode classifier can't decide, you no longer get a bogus denial message or permission-rule hint.

You'll notice Improvements
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
ImprovementsKind: in v2.1.225,
ImprovementsSection of the release
What

A permission decision that the classifier could not produce a verdict for is now tracked separately from a real denial, so telemetry and UI stop treating a classifier failure as a refusal.

Details
  • The decision reason carries a new noVerdict flag.
  • Denial-reason bucketing keys off the flag instead of matching a message prefix; telemetry labels are assembled at runtime as classifier:${e.classifier}:no-verdict around the literal :no-verdict.
  • The UI denial kind automode-parsing-error is now chosen by t.noVerdict.
  • The 'add a Bash permission rule' hint and the post-denial hook message are both skipped for no-verdict cases.
Evidence

noVerdict

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