Install CMX
CMX provides binaries for Linux, macOS, and Windows on x64 and ARM64. Install the coding client you want to use separately, and sign in to its model provider through that client.Standalone installer
- Linux and macOS
- Windows PowerShell
SHA256SUMS, and installs to /usr/local/bin when writable or ~/.local/bin otherwise. It then runs cmx setup --ask-connect-ready unless CMX_SKIP_START=1 is set.Connect ready agents during install
Before the standalone installer changes any coding client settings, it asks for your consent. After setup starts, CMX lists the coding clients and providers it found that are ready to connect, then asks:- Yes (
y): CMX routes every listed client through the local gateway. It also turns on a background check that runs at most once every 24 hours when you usecmxcommands to connect coding clients you configure later. - No (
n, or press Enter): CMX leaves your client settings unchanged. The 24-hour check stays off, and latercmx startruns don’t connect clients on their own.
cmx setup --ask-connect-ready in an interactive terminal.
If you declined, you can connect agents later. Run cmx setup --connect-ready to connect all ready providers and turn on the 24-hour check:
cmx harness enable <client> or the CONFIG screen in the cmx terminal interface.
The prompt concerns client routing, not CMX account registration. A CMX account is optional for local use. Provider sign-in remains in the coding client.
npm or pnpm
If you already use Node.js, install the published package:cmx setup --ask-connect-ready if setup has not run. Check the package’s current Node.js requirement with your package manager; the binary itself does not require Node.js.
Verify and connect
n at installation or use Undo and uninstall later.
Uninstall
To remove CMX, run:The documented behavior follows the current source. Check
cmx --version when using an older published release; options and supported clients can differ.