{"version":"2.1.229","anchor":"artifact-watches-can-wake-on-comments-and-say-why-they-did-n","canonical_anchor":"artifact-watches-can-wake-on-comments-and-say-why-they-did-n","heading":"Artifact watches can wake on comments, and say why they did not","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/artifact-watches-can-wake-on-comments-and-say-why-they-did-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Artifact watches can wake on comments, and say why they did not\n\nWatching an artifact could wake on new comments, not just republishes, but it's server-gated off.\n\n**What**\n\nIn 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.\n\n**Details**\n\n- 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)\".\n- The gate is `tengu_scalable_quiche`, alongside `CLAUDE_CODE_REMOTE`.\n\n**Evidence**\n\n`This remote session's durable wake rail was skipped as well`\n\n- Flag `tengu_scalable_quiche`: Off in both readings (read for one account on one subscription tier against v2.1.229; this account: off, anonymous baseline: off, compiled default: 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.\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}