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

Claude Code v2.1.257 ·

Artifact comments: retryable network/relay errors now flagged explicitly

Fetching artifact comments now flags retryable network and 429/5xx failures and honors a Retry-After header.

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

Fetching artifact comments now distinguishes retryable failures, such as network errors, HTTP 429/5xx, or relay-unavailable responses with certain statuses, from other failures via an explicit retryable flag, and honors a Retry-After header when present, instead of returning a generic failure uniformly.

Read from
Names in the bundleRetry-After
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up Retry-After, on routines-fire. | 429 | `rate_limit_error` | An hourly fire limit for the routine or the account has been reached. The response includes a `Retry-After` header indicating when the window resets. | api/claude-code/routines-fire see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up Retry-After, on routines-fire.

See this entry in the whole of v2.1.257 →

Feedback