Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.261 ·

Server-side auto-mode dangerous-tool-use classifier

Auto mode's dangerous-action classifier now runs server-side and blocks actions it flags or can't reach.

You'll notice Improvements
JSON All of v2.1.261
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Auto Mode SafetyArea: what it touches
ImprovementsKind: in v2.1.261,
ImprovementsSection of the release

Auto mode's server-side dangerous-tool-use classifier is expanded: API requests now carry a safeguards: [{ type: "dangerous_tool_use", context }] field, riding on a new anthropic-beta header entry, and the response's streaming deltas are parsed for matching safeguard_results against a schema of per-tool-call outcomes (flagged, not_flagged, skipped, unavailable). When flagged, the action is blocked with reason 'The server-side auto mode classifier judged this action dangerous'; if the server call is unavailable or times out, it blocks for safety with 'Classifier unavailable - blocking for safety'. The auto-mode fast-path check can now await a server classifier result and fall back to asking the user if the classification changed while queued (mode_changed_while_queued), recording telemetry fields classifierSource: server and serverClassifierNoVerdict, and a tengu_auto_mode_fallback_to_ask event.

What has happened since
Flag reading moved The flag server now returns on for tengu_smooth_chipmunk, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_smooth_chipmunk, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_smooth_chipmunk, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_smooth_chipmunk, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_smooth_chipmunk, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_smooth_chipmunk, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_smooth_chipmunk, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_smooth_chipmunk, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_smooth_chipmunk

See this entry in the whole of v2.1.261 →

Feedback