Product services
Cmdop separates three concerns: the cmdop binary on your own machine, which
holds the agent, the session, the relay and the web console; the account, plan
and marketplace services Cmdop operates; and the inference service the execution
engine calls. Each uses its own credential, and each can fail without the others.
Cmdop keeps three concerns apart, and it matters because they use different credentials and fail independently.
On your machine. The cmdop binary holds the agent that executes work and
the session that survives your disconnect. It also contains the relay and its
embedded web console, so one binary is the whole deployment unit — see
Deployment.
Operated by Cmdop. Account, plan, and marketplace services, plus the public relay edge if you chose that reachability mode. These are operated services, not something you install. Billing lives here — see Billing.
Inference. The CMDOP execution engine calls the CMDOP Router for inference. You configure that one credential — your platform API key — on the relay, under Settings → AI Providers.
Coding-agent CLIs you already have installed — Claude Code, Codex — stay separate products with their own accounts. Cmdop drives them as engines; it does not manage or replace their sign-in.
Credentials are separate on purpose
Browser console sessions, the fleet join key, per-machine connection PINs, and your inference credential are distinct. Rotating one does not silently rotate another. See Security.
Common questions
What runs on my machine?
The cmdop binary runs on your machine. It contains the local agent, session
state, relay, and embedded console for that deployment.
Which services does Cmdop operate?
Cmdop operates account, plan, marketplace, and public relay edge services. These are separate from the binary you run on your machine.
Does Cmdop manage my Claude Code or Codex account?
No. Claude Code and Codex stay separate local CLIs with their own sign-in. Cmdop can drive them as execution engines, but it does not own their accounts.
Cmdop