Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.275entry #147

Claude Code v2.1.275 ·

Artifact network and boot errors gain a transient flag and richer diagnostics

Artifact tool network and boot failures now carry a transient flag plus more diagnostic detail like status, timing, and port requirements

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

What

Error handling for the Artifact tool's network and boot requests was made more informative:

  • When an artifact content fetch fails with a plain network error, the message now explicitly states that outbound HTTPS on port 443 is required for the Artifact tool, instead of a generic "network error".
  • A new transient flag is now attached to some of these failures, marking them as potentially temporary.
  • Artifact publish/boot-error telemetry now includes the original request, HTTP status, and sync/agent/relay context flags when the error is a boot request or failure.
  • Boot-request network failures are now also tagged with wall-clock timing (wall_elapsed_ms) and a relay flag, alongside the existing error code.

Why

These changes make it easier to diagnose why an artifact failed to load or publish, and let callers distinguish transient (likely retryable) network problems from persistent ones.

See this entry in the whole of v2.1.275 →

Feedback