Claude could answer an artifact summon the first time it sees a thread, but the switch is off.
First-sight summon pickup sits behind CLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK or a remote gate that falls back to false.
tengu_gorse_pylon Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.237: on
Read once, for one account on one subscription tier, against v2.1.237. 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 auto-reacts to comments on an artifact, it can now pick up a recent summon the first time it sees a thread, not only on later sightings. The branch runs when CLAUDE_CODE_ARTIFACT_COMMENT_FAST_ACK is set, otherwise it consults the remote gate tengu_gorse_pylon, whose fallback is false. With no server value, the new branch never runs and only the previous pickup path applies.
- Telemetry reports the outcome: an
artifact_comments_autoreactevent flagsfirst_sight_summonwhen summons were found, or gives the rejection reasonfirst_sight_summon_stalewhen candidates existed but all were too old. - Covers both the branch that baselines a newly seen thread and the re-sighted branch.
- The gate helper itself already existed; only this use of it is new.
first_sight_summon_stale
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.
-
v2.1.232
Quick acknowledgement before the full artifact comment reply
Both mention comment fast
-
v2.1.235
Fixed-menu fast acknowledgment for artifact comments, behind two nested off-by-default gates
Both mention comment fast
-
v2.1.235
Artifact MCP is on by default
Both mention comment