Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.281entry #266

Claude Code v2.1.281 ·

Policy-limits fetch retries after an invalid-format (parse_failed) response even when retries are otherwise skipped

A malformed policy-limits response is now retried even when retries are otherwise switched off, instead of being given up on

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

Unclear The finding does not say which of tengu_shimmying_stardust and tengu_policy_limits_fetch sets skipRetry.

What

Claude Code fetches policy limits from a server. A response that does not match the expected format is now marked with the error code parse_failed. The retry and stale-fallback path, which tries again or falls back to older saved data, now runs for parse_failed even when skipRetry is set.

Whether skipRetry is set depends on a server-controlled switch. When that switch is on, a malformed response now triggers another attempt instead of Claude Code giving up.

Why

A garbled server response no longer ends the policy-limits fetch where it previously would have.

Read from
Feature flag
tengu_shimmying_stardust Off in both readings

The 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.281: 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.281. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns off for tengu_shimmying_stardust, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_shimmying_stardust, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_shimmying_stardust, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_shimmying_stardust, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

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 doubtThe finding does not say which of `tengu_shimmying_stardust` and `tengu_policy_limits_fetch` sets `skipRetry`.
Anthropic's release notes agreeImproved screen-reader output in /mcp: a disabled server is read as "off" instead of "pending"

See this entry in the whole of v2.1.281 →

Feedback