{"version":"2.1.300","anchor":"artifact-comment-auto-reply-classifier-unavailable-handoff","canonical_anchor":"artifact-comment-auto-reply-classifier-unavailable-handoff","heading":"Artifact comment auto-replies now log why they hand off when the checker is down","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/artifact-comment-auto-reply-classifier-unavailable-handoff","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Artifact comment auto-replies now log why they hand off when the checker is down\n\nAutomatic replies to artifact comments now record a reason when the checker that decides on replies is unavailable and the reply is handed off\n\n**Unclear.** Whether this handoff changes anything you see in artifact comments is not clear.\n\n**What**\n\nClaude Code can reply on its own to comments left on artifacts. A classifier, a check that decides whether to reply, guides this. When that checker is unavailable, Claude Code now records a diagnostic event saying the reply was handed off, along with a reason, for example:\n\n- another notified page already handles the comment threads\n\n- the comment was already notified\n\n- an edit has already gone in\n\n- automatic replies were stopped\n\n- the feature is switched off\n\nThe reasons a reply is held back are now named values instead of a simple yes or no.\n\n**Why**\n\nThis is mainly diagnostic information about automatic replies.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}