What
The daemon is a background process Claude Code can run. When it does not respond, claude daemon stop now:
- asks it to stop with SIGTERM (a polite stop request) and waits
- if it is still running, force-kills it with SIGKILL (a stop the process cannot ignore)
- refuses to signal process 1, the system's own first process
- explains when the process belongs to another user, so this account cannot signal it
Other failures come with detailed guidance instead of the single generic error from before.
Why
A 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.
Names in the bundleclaude daemon stop
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up claude daemon stop, on Run Claude Code behind a corporate launcher.
A running background service and any open `claude` sessions read the variable once at startup, so they keep launching unwrapped processes until restarted. Run `claude daemon stop --any` to stop the on-demand service. The next command that …corporate-launcher see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude daemon stop, on Run Claude Code behind a corporate launcher.
Anthropic's release notes agree
Fixed claude daemon stop exiting with no output, and leaving sessions listed as running, when telemetry is turned off