Sign-in connections
Cmdop deliberately does not have one sign-in. The account console uses your Cmdop account, a relay’s web console uses that relay’s own admin password or a one-time link, a machine joins the fleet with the join key, and coding-agent CLIs keep their own accounts. Most people come here after assuming one credential covers all four.
The account console at my.cmdop.com uses your Cmdop account. Manage how you sign in to it there.
A relay’s web console uses that relay’s own admin password, or a one-time sign-in link. A browser on the relay’s own host is recovered automatically through the loopback policy. See The web console.
A machine joins a relay with the fleet join key, not with any account sign-in. See Self-hosted relay or start from Quickstart.
Coding-agent CLIs — Claude Code, Codex — keep their own accounts and their own sign-in. Cmdop drives them as execution engines; it never manages their credentials.
Common questions
Why are there multiple Cmdop sign-ins?
Cmdop separates account identity, relay administration, machine joining, and external CLI accounts because each credential protects a different boundary.
Which credential joins a machine to a relay?
A machine joins a relay with the fleet join key. It does not use your account console sign-in for that operation.
Does Cmdop store my Claude Code or Codex sign-in?
No. Claude Code and Codex keep their own local CLI accounts. Cmdop can drive those CLIs, but it does not manage their credentials.
Cmdop