{"version":"2.1.247","anchor":"artifact-auto-replies-stay-pointed-at-the-session-that-armed","canonical_anchor":"artifact-auto-replies-stay-pointed-at-the-session-that-armed","heading":"Artifact auto-replies stay pointed at the session that armed them","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/artifact-auto-replies-stay-pointed-at-the-session-that-armed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Artifact auto-replies stay pointed at the session that armed them\n\nArtifact comment auto-replies now stay bound to the session you armed them from.\n\n**What**\n\nThe setup that lets Claude Code auto-reply to comments on an artifact now records whether it was captured during a human turn. A human-turn capture is kept, along with its session context and its transcript publisher, instead of being overwritten by later setup that did not come from a human turn.\n\n**Details**\n\n- Callbacks gained an accessor that hands back the live setup only when that setup is a human-turn capture or the caller is not itself a human turn.\n- Effect: a background publish or an automated arming can no longer silently repoint auto-replies at a different session's context.\n- No flag or environment variable guards this; it applies wherever artifact auto-reply is armed on this build.\n\n**Evidence**\n\n`humanTurnSnapshot`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}