{"version":"2.1.222","anchor":"artifact-comments-use-server-delivery-timestamps","canonical_anchor":"artifact-comments-use-server-delivery-timestamps","heading":"Artifact comments use server delivery timestamps","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/artifact-comments-use-server-delivery-timestamps","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Artifact comments use server delivery timestamps\n\nArtifact comments track when the server delivered them, so you should stop seeing the same comment twice.\n\n**What**\n\nComment state now records when the server actually handed a comment to Claude, and the client uses that instead of local bookkeeping to decide what has already been shown.\n\n**Details**\n\n- The comment schema gained sent_to_claude, sent_to_claude_degraded and awaiting_reply.\n- The client maps the server's to_claude_at into toClaudeAt and toClaudeAtDegraded.\n- A helper parses the timestamp and returns null when it cannot be parsed, so an unreadable value is treated as not-yet-delivered rather than crashing.\n\n**Evidence**\n\n`to_claude_at`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}