{"version":"2.1.273","anchor":"update-and-restart-messages-drop-the-artifact-comment-moni","canonical_anchor":"update-and-restart-messages-drop-the-artifact-comment-moni","heading":"\/update and \/restart messages drop the artifact-comment-monitor special casing","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/update-and-restart-messages-drop-the-artifact-comment-moni","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### \/update and \/restart messages drop the artifact-comment-monitor special casing\n\n\/update and \/restart no longer mention artifact comment monitoring in their refusal messages\n\n**Unclear.** Nothing has been read yet about the `tengu_update_refused` or `tengu_update_bg_respawn` gates mentioned alongside this change.\n\n**What**\n\nWhen `\/update` or a restart is refused, for example because the session was resumed from a different project directory or a background task is running, the message no longer checks whether an artifact 'comment monitor' task is active and no longer adjusts its wording for that case. The messages for transcript-path drift and for background tasks running are now fixed text, without the earlier note that restarting would stop auto-replies to artifact comments.\n\n**Why**\n\nThe refusal messages are simpler and no longer vary based on whether artifact comment monitoring happens to be running, so the caveat about losing auto-replies to comments is no longer shown even if that monitoring is active.\n\n- Area: Elsewhere\n- Names: `\/update`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}