Skip to content

cli-daemon.md

Latest commit

 

History

History
100 lines (73 loc) · 2.82 KB

cli-daemon.md

File metadata and controls

100 lines (73 loc) · 2.82 KB
Raw
summary Daemon lifecycle subcommands.
read_when
Looking up daemon subcommands
title coven daemon
description Reference for coven daemon: start, stop, restart, and status subcommands for the Rust daemon process that owns sessions and the local socket API.

coven daemon manages the local background process that owns session runtime, socket API state, and health reporting.

coven daemon status

Commands

Command Action
coven daemon start Start the daemon if it is not already running. Reuses a verified live daemon.
coven daemon status Print stopped/running/stale status, pid, socket path, and health flag. --json prints the same fields as one JSON document (status, ok, pid, socket, started_at).
coven daemon restart Stop the current daemon if present, then start a daemon with the current binary.
coven daemon stop Stop the daemon for the active COVEN_HOME.
coven daemon serve Hidden foreground server entrypoint used by the background launcher and supervisors.

First-run sequence

coven doctor
coven daemon start
coven daemon status

Expected running output:

Coven daemon: running (pid 12345, socket /home/alex/.coven/coven.sock)

For scripts, coven daemon status --json prints the same state as JSON with an ok field that reports whether the daemon health endpoint responded through the local socket.

Restart after upgrades

Restart after replacing the CLI binary, changing PATH, or switching COVEN_HOME:

coven --version
coven daemon restart
coven daemon status

The restarted process uses the executable that launched the command. This keeps npm, cargo, and source-checkout installs from accidentally leaving an old daemon behind.

State directory

Daemon metadata and the socket live under the active COVEN_HOME.

macOS/Linux/WSL2:

export COVEN_HOME="$HOME/.coven"
coven daemon status

PowerShell:

$env:COVEN_HOME="$env:USERPROFILE\.coven"
coven daemon status

Keep COVEN_HOME on a local per-user filesystem. For WSL2, use the WSL filesystem, not a mounted Windows path. For containers, bind-mount a persistent directory if sessions must survive container restarts.

Supervisor use

For systemd, launchd, tmux, or container entrypoints, prefer the foreground server command inside the supervisor:

coven daemon serve

Use coven daemon status from an interactive shell with the same COVEN_HOME to verify the supervised daemon.

Troubleshooting

  • not running: run coven daemon start.
  • stale: run coven daemon stop, then coven daemon start.
  • Permission errors: verify the daemon user owns COVEN_HOME.
  • Version drift: run coven --version, then coven daemon restart.

See Daemon will not start for deeper recovery steps.