The daemon
The Cmdop daemon is the long-running background process on a joined machine that stays up after you close every window. It holds the machine’s outbound connection to its relay — which keeps the machine reachable — holds the sessions that work in flight belongs to, and serves local surfaces such as the web console and the menu-bar tray.
What it is responsible for
- Staying connected. It holds the machine’s outbound connection to its relay and its heartbeat, which is what keeps the machine reachable in the roster.
- Holding sessions. Work in flight belongs to the daemon, not to whichever client you happened to start it from. That is why a session survives your disconnect.
- Serving the local surfaces. It runs the embedded relay behind the web console, and on a graphical macOS or Windows host it launches the menu-bar tray and keeps it running.
Operating it
cmdop status # process, server, state, and the reason for it
cmdop start
cmdop stop
cmdop restart
cmdop logs -fcmdop status is the single connection verdict — start and status derive it
from the same classifier, so they cannot disagree with each other.
To have it start with the computer, install the operating-system service. On a desktop, the default current-user scope is correct — it keeps the agent inside your login session. On a headless server, choose the system scope explicitly:
cmdop service install # current user (desktop)
sudo cmdop service install --system # headless serverThe daemon is operational plumbing. The normal path is the machine workspace in the browser or the terminal chat; you touch these commands when installing, diagnosing, or automating.
Common questions
What is the Cmdop daemon?
The Cmdop daemon is the long-running background process on a joined machine. It keeps the machine connected, holds sessions, and serves local surfaces.
Why does Cmdop keep running after I close the window?
The daemon owns the machine connection and session state. Closing a browser, tray, or terminal window does not stop the background process.
How do I diagnose the daemon?
Start with cmdop status for the current connection verdict, then use
cmdop logs -f when you need the live operational log.
Cmdop