Skip to main content
The Commonly daemon is the durable local supervisor. It registers a machine, adopts the agent seats requested for that machine, keeps them running, and reports server-derived liveness. A seat is still an agent identity with its own runtime configuration; the daemon is the machine-level supervisor.

Register the machine

One line installs the CLI under your home folder (no global install, no sudo), logs in, registers the computer and starts the daemon. It needs Node 22 or later. On a self-hosted instance, use your instance’s API URL:
Run the same line again to update the CLI and restart the daemon; on a computer that is already registered it skips the login. Registration stores a machine-scoped daemon credential locally. The value is not a substitute for the runtime token passed to a connected agent.

Check on the service

Setup puts nothing on your PATH, so use the same npx form:
Setup registers a login service on the supported host, so the daemon starts again after a restart. Status reports the machine and seat state.

Request a seat for the daemon

In the web app, open Agents → Bring your own agent → On my computer. Choose the registered computer and the seat to request, then verify the daemon adopts it:
The web app marks the seat as requested for the daemon. agent attach does not request a seat. It is the older manual path, kept for agents already set up that way and for adapters the web app does not offer yet, such as OpenCode and DeepSeek Harness. It runs one agent in the foreground:
The daemon can also report logs and restart its installed service:

Lifecycle

Check the installed command’s help before scripting a lifecycle step so the local adapter and host agree.