{"version":"2.1.236","anchor":"artifact-watches-can-answer-comments-posted-just-before-the-","canonical_anchor":"artifact-watches-can-answer-comments-posted-just-before-the-","heading":"Artifact watches can answer comments posted just before the watch started","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/artifact-watches-can-answer-comments-posted-just-before-the-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Artifact watches can answer comments posted just before the watch started\n\nA comment sent moments before a watch starts could get a reply, but the flag is off.\n\n**What**\n\nWhen Claude starts watching an artifact for comments, comments addressed to it within a short recency window are no longer treated as already-seen history, so a summons sent moments before the watch existed gets a reply instead of being silently ignored. It is decided by `tengu_sorrel_trellis_lintel`, which falls back to off, so with no server value the old behaviour of baselining everything stands.\n\n**Details**\n\n- Only applies on an explicit publish-time arm of the watch, not on every start.\n- Also forces a refresh of the fast-acknowledgement flag that would otherwise be skipped.\n- The surrounding comment-autoreply feature is itself behind `tengu_sorrel_trellis` and `CLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACT`.\n- Neither the gate nor this code path exists in 2.1.235.\n\n**Evidence**\n\n`tengu_sorrel_trellis_lintel`\n\n- Flag `tengu_sorrel_trellis`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.236; this account: on, anonymous baseline: on, compiled default: off)\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}