Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.257 ·

Artifact live-subscribe gains a second, non-websocket "sync" transport

Live artifact connections can use a new sync transport alongside websockets, with its own keepalive and reconnect logic.

TierNothing to try yethow much it should matter to you
Useful4my rating, 1 to 5
Signal4worth watching, 1 to 5
AreaArtifactswhat it touches
KindIn Developmentin v2.1.257,
Nothing to try yet Notable No documentation found

Live artifact connections can use a new sync transport alongside websockets, with its own keepalive and reconnect logic.

The artifact-watch supervisor that keeps a live connection open on a published artifact for auto-reply/reconnect logic can now open either the old websocket transport or a new sync transport, which has its own URL builder, dedicated ping-frame keepalive, and 404/expiry-based reconnect detection. Telemetry marks these connections with sync_transport: true in the artifact_live_subscribe event. The live-subscription bootstrap logic now distinguishes a lease's transport as live or sync, validates sync leases against stored credentials, and returns a new sync_unavailable outcome when sync can't be established.

Read from
Names in the bundlesync_transport

See this entry in the whole of v2.1.257 →

Feedback