Problem
After cargo install --path crates/kild-daemon, old daemon processes keep running from the previous binary path. New sessions auto-start a daemon if none is running, but if an old one is still alive, sessions route through it.
Observed
Two kild-daemon processes running simultaneously from target/release/kild-daemon (days old), while ~/.cargo/bin/kild-daemon is the newly installed binary.
Impact
Sessions may run on stale daemon code after upgrades, causing hard-to-debug behavioral differences.
Considerations
- Should there be only one daemon per machine? Currently per-project isolation is possible but not enforced.
kild daemon stop exists but isn't called during install.- A daemon restart command or automatic restart on binary change could help.
- At minimum,
kild daemon status should warn if the running binary differs from the installed one.
Problem
After
cargo install --path crates/kild-daemon, old daemon processes keep running from the previous binary path. New sessions auto-start a daemon if none is running, but if an old one is still alive, sessions route through it.Observed
Two
kild-daemonprocesses running simultaneously fromtarget/release/kild-daemon(days old), while~/.cargo/bin/kild-daemonis the newly installed binary.Impact
Sessions may run on stale daemon code after upgrades, causing hard-to-debug behavioral differences.
Considerations
kild daemon stopexists but isn't called during install.kild daemon statusshould warn if the running binary differs from the installed one.