Watching an artifact could wake on new comments, not just republishes, but it's server-gated off.
Comment-triggered artifact wakes are built but need a remote flag that falls back to false plus remote-session mode.
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.229: 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.229. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
In remote sessions, watching a published artifact can now register a wake that fires on new comments as well as republishes, and the tool text was rewritten to match. The whole durable wake path is behind a remote-config flag whose built-in fallback is false, so it is off unless the server turns it on, and it also requires the remote-session mode.
- Watch results can carry a skip reason, shown as "durable wake subscriptions are not enabled for this session" or "no wake-webhook minter is available (the session's own MCP mount was not found)".
- The gate is
tengu_scalable_quiche, alongsideCLAUDE_CODE_REMOTE.
This remote session's durable wake rail was skipped as well
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.