Run a long-lived agent
To keep a server permanently available in Cmdop, install the binary, run cmdop join <join-key> and cmdop start, then register it as an operating-system
service so it survives reboots. On a headless host use sudo cmdop service install --system, because the agent must run outside any login session. cmdop status is the verdict on whether it is connected.
On a server or other always-on host, install the binary, join the machine to a fleet, and start its agent:
curl -fsSL https://install.cmdop.com | sh
cmdop join <join-key>
cmdop start
cmdop statuscmdop status is the connection verdict — start and status derive it from
the same classifier, so they never disagree. If the join is rejected, request
a current join key and join again.
A headless host has no browser and no menu-bar tray. Bare cmdop on such a host
opens the terminal chat; use cmdop chat -p "..." for a single scripted prompt.
Start at boot
Install the operating-system service. On a headless server the agent must run outside a login session, so choose the system scope explicitly:
sudo cmdop service install --system
cmdop service statusWithout --system, cmdop service install registers a current-user service —
the right choice on a desktop, where it keeps the agent inside your login
session. The command reports unsupported platform combinations rather than
silently selecting an alternative.
Operate the agent
cmdop restart
cmdop logs -f
cmdop statusKeep it updated
cmdop update check # is a newer build available
cmdop update apply # install a pending update
cmdop update schedule # configure the automatic-update scheduleUse your normal host supervisor when an OS service is unavailable.
Common questions
How do I keep Cmdop running on a server?
Install the binary, join the server with cmdop join <join-key>, start the
agent, and install an operating-system service. On a headless server, choose the
service scope deliberately so the agent can run after your login session ends.
What command tells me if the agent is connected?
Use cmdop status. It reports the same connection verdict used by cmdop start, including whether the process is running, whether the relay is
reachable, and whether authentication was accepted.
Should a long-lived server auto-update?
Cmdop updates automatically by default. Keep that default for most machines, switch to notify-only when an operator must approve maintenance, or pin a version for locked-down environments. See Update Cmdop.