{"version":"2.1.295","anchor":"policy-limits-404304-no-cache-shortcut-now-also-requires-an","canonical_anchor":"policy-limits-404304-no-cache-shortcut-now-also-requires-an","heading":"Fewer sessions run without policy limits when none can be fetched","tier":"notice","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/policy-limits-404304-no-cache-shortcut-now-also-requires-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Fewer sessions run without policy limits when none can be fetched\n\nWhen policy limits cannot be fetched and none are saved, Claude Code now needs one more condition before running without restrictions\n\n**Unclear.** It is not stated what the new check tests, so it is unclear which sessions still run without restrictions.\n\n**What**\n\nWhen Claude Code asks for your organization's policy limits and the server answers with HTTP status 404 or 304, and there is no saved copy, it can fall back to running with no restrictions for that session. That fallback is not saved for later sessions.\n\nThat fallback now also requires a new check to come out false, alongside the existing condition. Sessions where the new check is true no longer take the no-restrictions path and are handled another way.\n\n**Why**\n\nThis narrows the cases where Claude Code runs without your organization's limits because it has no policy to read.\n\n- Flag `tengu_rustling_orbit`: Off in both readings (read for one account on one subscription tier against v2.1.295; this account: off, anonymous baseline: off, 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: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}