Artifacts could keep being watched even when your session is not running, but that is off.
Server-side webhook-backed durable artifact watches are fully built behind a flag that is off in this build.
tengu_scalable_quiche Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.227: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.227. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
New machinery keeps watching a published artifact even when the session is not live, by minting a webhook through a dedicated wake service (watch_url and unwatch_url tools) and subscribing to the artifact's publish events. Unsubscribing releases both the subscription and the webhook. It requires a first-party client and the flag tengu_scalable_quiche, which is off in this build.
- the returned https URL is checked against the expected webhook path shape before being used
- outcomes are reported as
artifact_durable_subscribewith reasons including trigger_limit, mint_failed, no_wake_minter and client_policy
artifact_durable_subscribe
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.