What
When the background daemon service finds that its launcher binary has been deleted or replaced (as happens after a version upgrade), it regenerates the service file from current settings rather than crash-looping.
Details
- New logic distinguishes between three failure modes: the service file points at a binary that no longer exists, the launcher setting changed, and the daemon is running unwrapped (without the corporate launcher when required).
- The
"installed service starts through a launcher that was deleted or is no longer executable — regenerating the service file from the current settings"message indicates self-healing was triggered. claude daemon installcan be run manually to force a clean repair.
Evidence
Self-heal path (search for "installed service starts through a launcher that was deleted or is no longer executable — regenerating the service file from the current settings")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.