{"version":"2.1.247","anchor":"artifact-comment-watchers-can-be-restored-after-a-headless-r","canonical_anchor":"artifact-comment-watchers-can-be-restored-after-a-headless-r","heading":"Artifact comment watchers can be restored after a headless resume","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/artifact-comment-watchers-can-be-restored-after-a-headless-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Artifact comment watchers can be restored after a headless resume\n\nArtifact comment watchers can be restored after a headless resume by rescanning the transcript.\n\n**What**\n\nBackground watchers that report new comments on an artifact can now be re-established when a session resumes on a host surface, by rescanning the end of the session transcript instead of relying on the newer session-record store.\n\n**Details**\n\n- The rescan reads the transcript from a saved byte offset and refuses if the file shrank, or grew by more than 8 MB, or if the appended region does not start on a line boundary and end with a newline.\n- Only watcher records whose session id matches the current session are replayed.\n- The watcher messages gained a host-surface variant that drops the `\/tasks`, `\/login` and `claude agents` suggestions, since those commands do not exist on those surfaces.\n\n**Evidence**\n\n`artifact-comment-monitor`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}