Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.292entry #151

Claude Code v2.1.292 ·

Artifact publishing gains a frame-routed content fetch and clearer gateway errors

Artifact deploys can fetch content through a frame route with retries, and failed later sends now give a clearer cloud gateway error

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

What

Artifacts are files or pages Claude can publish for you. Publishing them changed in two connected ways:

  • New helpers fetch artifact content from /api/frame/content/... with an x-frame-asset-token header. They retry on 429 and 503 errors and accept the response only when x-frame-content-route is "served".
  • This path is used when contentVia === "frame" and is skipped when CLAUDE_CODE_REMOTE is set.
  • The deploy function takes a new flag. When a later send of a publish is cancelled or the cloud session's gateway fails, it now reports 'a later send of this publish could not go through the cloud session's gateway'. Before, failures only said 'relay request failed' or 'deploy request failed'.
  • The relay code now uses a shared helper for working out content types, which used to be defined locally.

Why

When publishing an artifact from a cloud session fails part way, the message now says where it went wrong. Busy or briefly unavailable servers are retried instead of failing straight away.

See this entry in the whole of v2.1.292 →

Feedback