Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.225 Home All releases ←olderv2.1.224 v2.1.226newer→
Claude Code v2.1.225

Artifact publishes retry 429 and 503 with a live progress line

You'll notice
Useful4 Signal0
Artifacts

Artifact publishing now retries when the service is busy, showing a live attempt counter instead of failing.

What

Publishing an artifact through /api/frame/deploy/direct now retries transient failures instead of failing outright, and shows the retry state while it happens.

Details
  • A 429 is retried once after the retry-after delay, capped; 503s are retried with backoff up to a maximum attempt count.
  • Retries honor the abort signal, logging "[artifact] /deploy/direct retry cancelled by user".
  • A new progress event type renders "Publish service temporarily unavailable" or "Publish service busy" followed by " — retrying (attempt N of M)…".
  • Telemetry deploy_503_retried / deploy_429_retried carries deploy_attempts and deploy_final_status.
  • onRetry and signal are threaded through the publish call chain. None of this existed in 2.1.224.
Evidence

artifact_publish_retry

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.225 →