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.234 Home All releases olderv2.1.233 v2.1.235newer
Claude Code v2.1.234

Publishing tells relay failures apart from real service answers

You'll notice
Useful2 Signal2
Artifacts

A publish answer that didn't come from the artifact service is reported as a relay error with its status.

What

When a publish, deploy or upload answer did not actually come from the artifact service, it is now reported as a relay error carrying the HTTP status and a message saying the publish was not completed, instead of being parsed as if it were a deploy result.

Details
  • Responses carry a marker recording whether they came from the artifact service itself.
  • New telemetry reasons: relay_error, upload_relay_error, prepare_upload_relay_error.
  • The related HTTP call sites dropped their per-call host, auth and status-validation options.
Evidence

prepare_upload_relay_error

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.234 →