Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.229 ·

Artifact watches can wake on comments, and say why they did not

Watching an artifact could wake on new comments, not just republishes, but it's server-gated off.

Nothing to try yet In Development
JSON All of v2.1.229
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.229,
What probably matters to youSection of the release

Comment-triggered artifact wakes are built but need a remote flag that falls back to false plus remote-session mode.

What

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.

Details
  • 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, alongside CLAUDE_CODE_REMOTE.
Evidence

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.

Read from
Feature flag
tengu_scalable_quiche Off in both readings

The 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: off

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 has happened since
Flag reading moved The flag server now returns off for tengu_scalable_quiche, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_scalable_quiche, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.229 →

Feedback