{"version":"2.1.259","anchor":"policy-limits-fail-open-on-404unsolicited-304-with-no-cache","canonical_anchor":"policy-limits-fail-open-on-404unsolicited-304-with-no-cache","heading":"Policy limits fail open on 404\/unsolicited 304 with no cache","tier":"notice","area":"Policy Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/policy-limits-fail-open-on-404unsolicited-304-with-no-cache","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Policy limits fail open on 404\/unsolicited 304 with no cache\n\nA missing policy-limits response with no cache no longer counts as a failure; the session runs with no restrictions instead.\n\nIn 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.\n\n- Flag `tengu_rustling_orbit`: Not enough to say (read for one account on one subscription tier against v2.1.259; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Policy Limits\n- Names: `tengu_rustling_orbit`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}