{"version":"2.1.300","anchor":"daemon-stop-now-escalates-sigterm-to-sigkill-and-explains-st","canonical_anchor":"daemon-stop-now-escalates-sigterm-to-sigkill-and-explains-st","heading":"claude daemon stop now force-kills a daemon that will not stop","tier":"notice","area":"Daemon","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/daemon-stop-now-escalates-sigterm-to-sigkill-and-explains-st","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### `claude daemon stop` now force-kills a daemon that will not stop\n\n`claude daemon stop` now asks a stuck daemon to stop, waits, then force-kills it, and explains clearly when it cannot\n\n**What**\n\nThe daemon is a background process Claude Code can run. When it does not respond, `claude daemon stop` now:\n\n- asks it to stop with SIGTERM (a polite stop request) and waits\n\n- if it is still running, force-kills it with SIGKILL (a stop the process cannot ignore)\n\n- refuses to signal process 1, the system's own first process\n\n- explains when the process belongs to another user, so this account cannot signal it\n\nOther failures come with detailed guidance instead of the single generic error from before.\n\n**Why**\n\nA stuck daemon can now be stopped without finding its process number and killing it by hand. When it cannot be stopped, the message says why.\n\n- Area: Daemon\n- Names: `claude daemon stop`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}