Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.307 ·

Policy status shows when cached restrictions still apply after a failed fetch

When fetching remote policy settings fails but a cached copy exists, the status now says the cached policy's restrictions still apply

Group of 2 You'll notice Improvements
JSON All of v2.1.307
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
ImprovementsKind: in v2.1.307,
ImprovementsSection of the release

What

Organizations can push settings to Claude Code from a server, known as remote settings or remote policy. When fetching them fails and a saved (cached) copy exists, the failure state can now carry restrictionsOnly: true.

When that state is set, the policy status line ends with "· the cached policy's restrictions still apply". Before, this situation showed "· no remote policy applied".

Why

The old wording suggested no policy was in force when the cached restrictions were in fact still in force. If you work under managed settings, the status now tells you that those limits remain even though the latest copy could not be fetched.

See this entry in the whole of v2.1.307 →

Feedback