{"version":"2.1.304","anchor":"mods-barred-from-starting-background-work-after-stop-toast","canonical_anchor":"mods-barred-from-starting-background-work-after-stop-toast","heading":"Mods can no longer start background work after you press Stop","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/mods-barred-from-starting-background-work-after-stop-toast","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Mods can no longer start background work after you press Stop\n\nAfter Stop, a mod's attempt to start background work is refused, and you see a notice that a mod cannot resume work after Stop\n\n**Unclear.** It is not clear what counts as a mod, or whether the block also applies to background work you start yourself.\n\n**What**\n\nAfter you stop Claude Code, a mod can no longer start new work that keeps running in the background. Claude Code refuses these requests and returns a message explaining why. They include:\n\n- subscribing to a pull request\n\n- starting a watch or a publish\n\n- running a command in the background\n\n- starting a schedule or a goal\n\nWhen this happens, a short pop-up notice reads: \"Stopped: type a message to continue; a mod cannot resume work after Stop\". To let work continue, type a new message.\n\n**Why**\n\nOnce you press Stop, work stays stopped. A plugin-driven mod cannot quietly start things up again until you send a message.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}