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.274 ·

Artifact requests gain explicit kind and watchBoot parameters

← All of v2.1.274 Home All releases

Artifact boot and fetch requests now take explicit kind (default 'probe') and watchBoot parameters instead of implicit behavior

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaArtifactswhat it touches
KindInternal Changesin v2.1.274,
Group of 2 Under the hood

Artifact boot and fetch requests now take explicit kind (default 'probe') and watchBoot parameters instead of implicit behavior

What

  • The artifact frame-boot request function now takes a kind parameter (defaulting to "probe") and a watchBoot flag. Probe requests append &bk=probe to the query string, while watch/sync/peer requests append a &vn= version parameter.
  • The artifact-fetch helper used by the publish/read flow likewise now takes kind (default "probe") and watchBoot, alongside its existing relayOnly/agentPeer/syncLive/speculative options, feeding into the same underlying request.

Why Making the request kind and boot-watching explicit lets the different artifact flows (probing, watching, syncing, peer requests) be distinguished consistently wherever an artifact request is made.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat effect the new `kind` and `watchBoot` parameters have on user-visible behavior isn't stated.

See this entry in the whole of v2.1.274 →

Feedback