Install the CLI
The Cmdop CLI installs from https://install.cmdop.com — pipe it to sh on
macOS and Linux, or download the .exe on Windows and put it on your PATH.
Verify with cmdop version, check the host with cmdop doctor, then join the
machine to a fleet with cmdop join <join-key>. There is no browser login and no
device-code flow.
Cmdop ships as one cross-platform binary called cmdop. There is no desktop
installer and no GUI setup: install the binary, verify it, join the machine.
macOS and Linux
curl -fsSL https://install.cmdop.com | shThe script detects your operating system and architecture, downloads the
matching build, places it on your PATH (/usr/local/bin by default, which may
prompt for sudo), writes a default configuration file, and registers a
background service for the current user.
To install without elevated rights, pass a writable prefix:
curl -fsSL https://install.cmdop.com | sh -s -- --prefix=$HOME/.local/binThe installer registers a current-user service so the agent keeps access to
your login session, its keychain, notifications, and deep links. A system-wide
service on a headless host is a deliberate administrator choice:
sudo cmdop service install --system.
If you install from the macOS .pkg instead, the package deliberately installs
only the binary. Sign in as the user who will run Cmdop and complete setup in
that session:
cmdop service installWindows
Windows uses the same single binary — download the executable and put it on your
PATH:
https://install.cmdop.com/cli/latest/cmdop-windows-x64.exeiwr -useb https://install.cmdop.com/cli/latest/cmdop-windows-x64.exe -OutFile C:\Tools\cmdop.exeSave it as cmdop.exe in a directory on your PATH (for example C:\Tools),
then open a fresh terminal.
Verify the install
cmdop versionYou should see a single line: CMDOP CLI version X.Y.Z. If you see
command not found, the install directory is not on your PATH — the install
script prints the exact export PATH=… line for your shell.
Then run the built-in diagnostic:
cmdop doctorcmdop doctor checks that the binary is on PATH, that configuration loaded,
whether native machine volumes are available on this host, and reports daemon
and connection status. At this point it correctly reports that the machine has
not yet joined a fleet — that is the next step.
Start this machine
With a fleet join key from the relay administrator:
cmdop join <join-key>
cmdop start
cmdop statusJoining starts the background agent unless you pass --no-agent. To join
against a specific relay, add --server <url> (and --insecure for a
self-signed self-host).
cmdop join is the whole sign-in story. There is no browser login and no
device-code flow; cmdop login is a retired compatibility command that errors
with a pointer to cmdop join.
Common questions
What is the Cmdop install command?
On macOS and Linux, run curl -fsSL https://install.cmdop.com | sh. On Windows,
download the cmdop.exe binary and put it on your PATH, then open a fresh
terminal.
Do I sign in with a browser after installing?
No. A machine joins a fleet with cmdop join <join-key>. There is no browser
login or device-code flow for bringing a machine online.
What should I run after installation?
Run cmdop version, then cmdop doctor, then cmdop join <join-key>. After
joining, cmdop status is the connection verdict for that machine.
Next steps
- Quickstart — join, open the workspace, first conversation.
- Run as a long-lived agent
- Connect a machine
- CLI reference
Cmdop