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.274entry #238

Claude Code v2.1.274 ·

Artifact requests gain explicit kind and watchBoot parameters

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

Group of 2 Under the hood Internal Changes
JSON All of v2.1.274
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.274,
Internal ChangesSection of the release

Unclear The finding doesn't describe any visible effect of this beyond the internal request format.

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 doubtThe finding doesn't describe any visible effect of this beyond the internal request format.

See this entry in the whole of v2.1.274 →

Feedback