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.280 ·

Refusal/safeguard handling gains a policy_refusal path

Refused evaluations can now produce a distinct 'policy_refusal' block reason instead of a generic unavailable one

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

When Claude Code cannot get an evaluation result because it was refused, it now can produce a specific blocking result with failure mode policy_refusal and reason category policy_refusal, rather than falling through to the generic 'unavailable' handling.

Why

This gives refusal-caused blocks a distinct, identifiable reason instead of lumping them in with other unavailable-result cases, which should make it clearer when a refusal specifically was the cause.

Read from
Names in the bundlepolicy_refusal
Feature flag
tengu_tranquil_summit Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.280: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.280. It isn't a statement about your account. What a flag value here can and cannot tell you

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_tranquil_summit

See this entry in the whole of v2.1.280 →

Feedback