Install

The daemon is distributed as @evoxiv/daemon on npm. The package itself is a tiny Node shim; the actual native binary ships in one of five platform sub-packages (@evoxiv/daemon-{linux,darwin,win32}-{x64,arm64}) that npm installs as an optional dependency matched against your OS and CPU.

You need:

• Node ≥ 18 on the install path (node --version). Bun is not required — the package's bin entry is a Node shim that locates and execs the platform binary.
• One of the supported targets: linux-x64, linux-arm64, darwin-x64, darwin-arm64, win32-x64.
• A backend CLI on PATH matching whatever backend your Agents use: claude for Anthropic Claude Code, codex for the OpenAI Codex CLI. The dry-run backend needs nothing.

Global install

npm i -g @evoxiv/daemon

This installs the shim into your npm global bin (visible as evoxiv-daemon) and pulls only the platform sub-package matching your host. The other four are skipped via npm's os/cpu filters — your install is one binary, not five.

Verify:

evoxiv-daemon --version
evoxiv-daemon --help

Project-local install

If you'd rather not install globally, drop it in a project:

mkdir evoxiv-daemon-host && cd evoxiv-daemon-host
npm init -y
npm i @evoxiv/daemon
npx evoxiv-daemon --token 'evxd_…'

The shim resolution rules are the same; only the install location differs.

Air-gapped / custom binary

The shim respects an override env var:

EVOXIV_DAEMON_BINARY=/opt/evoxiv/my-built-daemon \
  evoxiv-daemon --token 'evxd_…'

Use this when you've built the binary yourself (we don't yet publish binaries for every platform — see the supported list above) or when you're inside an environment that can't reach npm at install time. The override is the first thing the shim checks; if it's set, the platform sub-package isn't consulted.

Updating

The platform sub-package's version is pinned to the main package's version. Bumping with npm rolls them in lockstep:

npm i -g @evoxiv/daemon@latest

There is no separate upgrade for the binary.

Uninstalling

npm rm -g @evoxiv/daemon

This drops both the shim and the platform sub-package. It does not delete the workspaces directory the daemon used (see EVOXIV_WORKSPACES_DIR), so any in-flight task workdirs survive — delete them by hand if you need to fully clean up.