Unclear It is not clear whether old signed documents are now rejected somewhere else or not at all.
An organization can send Claude Code settings and policies, called managed settings, as signed documents. The signature proves they came from a trusted source. Before, Claude Code also remembered the newest issue time it had accepted. It rejected any document issued earlier than that as a "rollback". That check has been removed from the code that verifies these documents.
The way Claude Code fetches policy limits was also reworked.
The rollback check stopped an older, still validly signed document from replacing a newer one. Without it in this code, an outdated set of managed settings or policies would not be rejected here for its age. Administrators who rely on newer policies always taking effect should keep this in mind.
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.312: 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.312. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear whether old signed documents are now rejected somewhere else or not at all.