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
HomeReleasesv2.1.248entry #497

Claude Code v2.1.248 ·

Sync failures distinguish "lane unavailable" from "unsupported"

Sync errors now distinguish a server declining this path from one with no sync at all.

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

Session sync errors are classified more precisely, so a server that is declining this particular sync path is no longer reported the same as a server that does not support sync at all. Applies to everyone, no gate.

Details
  • HTTP 400 with a laneDenied reason becomes lane_unavailable.
  • HTTP 400 for upload or download unavailable becomes lane_unavailable with cause direct_sync_off.
  • 501 and 405 remain unsupported and now carry the status code.
  • 404 counts as not_found only outside the begin phase and only when the body is a not-found error.
Evidence

{ kind: "lane_unavailable", cause: "direct_sync_off" }

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

Feedback