Install the Cmdop CLI

Cmdop ships as a single cmdop binary. Install it from Cmdop’s distribution service.

macOS and Linux

curl -fsSL https://install.cmdop.com | sh

For an install that does not require writing to a system directory:

curl -fsSL https://install.cmdop.com | sh -s -- --prefix=$HOME/.local/bin

Make sure the chosen directory is on PATH, then open a new shell.

Windows

Run in PowerShell:

irm https://install.cmdop.com/install.ps1 | iex

This downloads the binary, verifies its checksum, installs it under %LOCALAPPDATA%\cmdop\bin, adds that directory to your user PATH, and registers the background service. Open a new PowerShell window afterwards so the updated PATH takes effect.

To install somewhere else, set the directory first:

$env:CMDOP_INSTALL_DIR="C:\Tools"; irm https://install.cmdop.com/install.ps1 | iex

Download the binary directly

Windows ships the same single executable, so you can skip the script entirely:

https://install.cmdop.com/cli/latest/cmdop-windows-x64.exe

Save it as cmdop.exe and move it into a directory that is already on your PATH. Installing this way is fully manual — nothing updates PATH or installs the service for you.

Put the binary on PATH afterwards

If you installed from the macOS .pkg, or the binary is somewhere your shell does not search, copy it into your user path:

cmdop setup

Run it once with the full path if cmdop is not resolvable yet:

/Applications/CMDOP.app/Contents/MacOS/cmdop setup

cmdop doctor --install-cli does exactly the same thing.

Verify the installation

cmdop version
cmdop --help

cmdop doctor reports the version, the binary paths it found, your PATH, login state, and agent status — run it when cmdop behaves as if it were a different installation than the one you expect.

Next, join a fleet with the join key supplied by the owner of the relay you want to join. To be walked through relay selection, joining, and a first conversation in one flow, run cmdop onboard.