A comment sent moments before a watch starts could get a reply, but the flag is off.
A recency window for pre-watch comments sits behind tengu_sorrel_trellis_lintel, which falls back to off.
tengu_sorrel_trellis On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.236: on
Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When 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.
- Only applies on an explicit publish-time arm of the watch, not on every start.
- Also forces a refresh of the fast-acknowledgement flag that would otherwise be skipped.
- The surrounding comment-autoreply feature is itself behind
tengu_sorrel_trellisandCLAUDE_CODE_ARTIFACT_COMMENTS_AUTOREACT. - Neither the gate nor this code path exists in 2.1.235.
tengu_sorrel_trellis_lintel
Strings lifted out of the shipped bundle, so the claim above can be checked against them.