Refused evaluations can now produce a distinct 'policy_refusal' block reason instead of a generic unavailable one
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.
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.
tengu_tranquil_summit Not enough to sayNothing 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
New in this build: tengu_tranquil_summit