{"version":"2.1.210","anchor":"daemon-service-launcher-self-healing","canonical_anchor":"daemon-service-launcher-self-healing","heading":"Daemon Service Launcher Self-Healing","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.210\/e\/daemon-service-launcher-self-healing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.210","markdown":"### Daemon Service Launcher Self-Healing\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- 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).\n- The `\"installed service starts through a launcher that was deleted or is no longer executable \u2014 regenerating the service file from the current settings\"` message indicates self-healing was triggered.\n- `claude daemon install` can be run manually to force a clean repair.\n\n**Evidence**\n\nSelf-heal path (search for `\"installed service starts through a launcher that was deleted or is no longer executable \u2014 regenerating the service file from the current settings\"`)"}