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.299 ·

Saved organisation policy limits are used only if their signed copy checks out

Claude Code now uses its saved copy of policy limits only when a signed copy verifies against the organisation; otherwise it starts without it

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

Unclear It is not known whether this stricter check is switched on for everyone or held behind a remote switch.

What

Policy limits are restrictions an organisation places on Claude Code, and Claude Code keeps a saved copy of them on disk. Until now a signed copy of that saved data was only checked in the background. The check did not decide anything, and the saved copy was used whenever its stamp matched.

Now the saved copy is trusted only if its signed copy verifies against the organisation the administrator pinned. If it does not verify, Claude Code starts as if nothing were saved. Compliance restrictions and explicit denials still apply in that case. Claude Code also records whether the stored copy was trusted, and records when the signed identity behind the cache changes.

Why

In organisations with managed settings, Claude Code may refuse a saved policy cache after an upgrade and fetch the limits afresh, which can show up as a slower or different start.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not known whether this stricter check is switched on for everyone or held behind a remote switch.

See this entry in the whole of v2.1.299 →

Feedback