Desktop treats any reachable cli-daemon manifest as an OS-supervised daemon.
Currently, the manifest schema has no supervised/lifecycle signal:
owner: {
client: "cli" | "desktop";
version: string | null;
executablePath: string | null;
}
But Desktop attaches with supervised semantics based only on kind: "cli-daemon":
if (!manifest || manifest.kind !== "cli-daemon") return { kind: "unavailable" };
and returns:
A foreground/user-started CLI daemon and a launchd/systemd daemon can both publish kind: "cli-daemon", so Desktop cannot distinguish them. This can make Desktop use supervised lifecycle behavior for a non-supervised daemon.
Desktop treats any reachable cli-daemon manifest as an OS-supervised daemon.
Currently, the manifest schema has no supervised/lifecycle signal:
But Desktop attaches with supervised semantics based only on kind: "cli-daemon":
and returns:
supervisedDaemon: trueA foreground/user-started CLI daemon and a launchd/systemd daemon can both publish kind: "cli-daemon", so Desktop cannot distinguish them. This can make Desktop use supervised lifecycle behavior for a non-supervised daemon.