Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.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.

TierYou'll noticehow much it should matter to you
Useful3my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaAuto Mode Safetywhat it touches
KindImprovementsin v2.1.261,
You'll notice

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

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.

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