A missing policy-limits response with no cache no longer counts as a failure; the session runs with no restrictions instead.
In the policy-limits fetch/cache loader, a 404 or an unsolicited 304 response with no local cache is no longer treated as a hard fetch failure. The client logs Policy limits: ${n.httpStatus} with no cache, no restrictions for this session (not persisted), applies an empty restriction object for that session, and records telemetry as route_missing_fail_open or unsolicited_304_fail_open. This fail-open path is gated by tengu_rustling_orbit, which defaults to off in the resolved gate table, so failing open is the default shipped behavior; turning the gate on remotely falls back to the old failure-closed path instead.
tengu_rustling_orbit 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.259: off
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.259. It isn't a statement about your account. What a flag value here can and cannot tell you
New in this build: tengu_rustling_orbit