Unclear It is not stated what the new check tests, so it is unclear which sessions still run without restrictions.
When 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.
That 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.
This narrows the cases where Claude Code runs without your organization's limits because it has no policy to read.
tengu_rustling_orbit Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.295: 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.295. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not stated what the new check tests, so it is unclear which sessions still run without restrictions.