Source Intelligence

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

Artifact publish now retries 503s with a visible progress line

You'll notice
Useful3 Signal0
Artifacts

Publishing an artifact now retries when the service is busy and tells you it is waiting.

What

Publish and deploy calls go through a shared retry wrapper that retries HTTP 503 using a delay derived from retry-after, and the transcript shows why it is waiting instead of appearing to hang.

Details
  • Retry progress is reported as an artifact_publish_retry event, rendered by a new UI component.
  • The line reads "Publish service temporarily unavailable" for a 503 and "Publish service busy" otherwise, followed by an attempt counter.
  • Telemetry records "deploy_503_retried" and "deploy_429_retried" with a deploy_attempts field.
Evidence

Publish service temporarily unavailable

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 →