Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

Policy limits fall back to a fresh default when the saved copy can't be used

If the saved policy limits can't be used, Claude Code now builds a fresh default state instead of having no policy answer at all

Under the hood Internal Changes
JSON All of v2.1.323
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
Internal ChangesKind: in v2.1.323,
Internal ChangesSection of the release

Unclear What the freshly built state contains, and so which limits apply when the saved copy is unusable, is not stated.

What

Claude Code keeps a saved copy, called a cache, of its policy limits information. Sometimes that saved copy can't be used, in any of these cases:

  • The cache is refused.
  • The cache can't be read.
  • The cache fails the check that decides whether it may be used.

In those cases, loading policy limits used to produce nothing. It now produces a freshly built state.

Why

When Claude Code starts without a usable saved copy, it now has a default policy answer to work from instead of none.

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 doubtWhat the freshly built state contains, and so which limits apply when the saved copy is unusable, is not stated.

See this entry in the whole of v2.1.323 →

Feedback