{"version":"2.1.271","anchor":"artifact-comment-auto-reply-gained-a-fork-gating-path","canonical_anchor":"artifact-comment-auto-reply-gained-a-fork-gating-path","heading":"Artifact comment auto-reply gained a 'fork' gating path","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifact-comment-auto-reply-gained-a-fork-gating-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Artifact comment auto-reply gained a 'fork' gating path\n\nArtifact comment auto-reply logic reworked with additional checks including a 'fork' gate\n\n**Unclear.** The finding does not explain what the individual checks (na, Wt, st, Un) verify or what a 'fork' state means for an artifact in this context.\n\n**What**\n\nThe logic that decides whether Claude automatically replies to a new comment on an artifact has been reorganized into new helper functions. It now runs several additional checks before deciding to auto-reply, including, in some cases, an extra asynchronous check tied to forking. If that check fails, Claude Code logs a `fork_gate_error` telemetry event instead of replying.\n\n**Why**\n\nThis adds more conditions that must pass before Claude auto-replies to an artifact comment, likely to avoid auto-replying in situations (such as certain forked artifact states) where it shouldn't.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}