Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

Auto-mode tool classification tightened with a new 'classifierAllowed' check

Auto-mode tool classification now tracks an explicit classifierAllowed flag on tool-use records before treating a decision as classifier-driven

Group of 2 Under the hood Internal Changes
JSON All of v2.1.280
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Auto ModeArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release

What

  • Tool-use records now carry a new autoModeClassified field (alongside toolUseId).
  • The autoModeClassified marker passed into a tool call now also requires decisionReason.classifierAllowed === true, in addition to the existing checks that decisionReason.type === "classifier" and classifier === "auto-mode".

Why This adds a stricter, explicit check before a tool call is treated as auto-mode classified, reducing the chance of misclassifying decisions.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what changes for the user when a call fails this stricter check.

See this entry in the whole of v2.1.280 →

Feedback