Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.247 ·

"Not served" is now distinct from "unavailable" for session-relayed calls

Artifact and asset calls your session can't relay now report as unsent rather than hard failures.

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

Calls that a session's connection declines to carry now report as unsent rather than as a hard failure, across Artifact startup reads, asset uploads/listing/deletes, comment resolve and reply, and summon status. Asset access gets a deny message explaining that uploads, listing and deletes are not available from this kind of session.

Details
  • The new reason is relay-not-served, separate from the existing relay-unavailable; Artifact startup reads log boot_relay_not_served.
  • The HTTP helper gained relay-bound and relay-only delete verbs.
Evidence

relay_not_served

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

Feedback