{"version":"2.1.222","anchor":"artifact-comment-auto-reply-understands-sent-to-claude-lanes","canonical_anchor":"artifact-comment-auto-reply-understands-sent-to-claude-lanes","heading":"Artifact comment auto-reply understands \"sent to Claude\" lanes","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/artifact-comment-auto-reply-understands-sent-to-claude-lanes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Artifact comment auto-reply understands \"sent to Claude\" lanes\n\nArtifact comment threads now track which comments were actually sent to you, and re-sending one triggers a reply.\n\n**What**\n\nComment threads are now classified per comment into human, agent and unknown lanes, and sending or re-sending a comment to Claude is itself a trigger for auto-reply rather than only a new comment being one.\n\n**Details**\n\n- each comment carries a lane; a `toClaudeAt` timestamp marks it as sent to Claude\n- new trigger kind `redesignated` covers existing comments newly toggled to Claude, tracked through a per-thread `sentToClaudeAt` map\n- the composed prompt now explains the row heads `[human]`, `[assistant]`, `[human, sent to you]` and `[unverified lane]`\n\n**Evidence**\n\n`A human sent an EXISTING comment in the thread to you on an artifact you published`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}