Skip to Content

Agents

The agent is Cmdop running on a joined computer. It is what turns a machine into something you can work with from anywhere.

The agent holds the machine’s execution authority: the files, the tools, the project folders, and the live sessions all belong to it. Everything else — browser, terminal, tray, SDK — is a client that attaches to what the agent already owns.

It dials out

An agent makes an outbound connection to its configured relay and keeps that connection open. Nothing dials in to the machine, which is why an agent works from behind NAT and from inside a network with no inbound port open.

That open connection is also what “online” means. A machine is reachable while its agent is connected; if the connection drops, the machine goes offline in the roster and nothing can route to it until it returns.

What it runs

The agent can use CMDOP’s built-in execution engine, or drive a locally installed coding-agent CLI — Claude Code or Codex — as the engine for a session. Cmdop uses those tools’ existing local sign-in; it never collects or manages their account credentials. See Execution engines.

Lifecycle

cmdop join <join-key> # join a relay; starts the agent cmdop status # the connection verdict cmdop start / cmdop stop / cmdop restart

cmdop start makes this machine reachable. It is not the command for reaching a different machine — that is cmdop connect. See the daemon for what runs in the background and Connect for reaching other machines.

Common questions

What does the Cmdop agent do?

The agent runs on a joined machine, owns that machine’s files, tools, project roots, and live sessions, and keeps an outbound connection to the relay. Clients attach to what the agent owns; they do not become the durable owner of the work.

Does the agent require inbound network access?

No. The agent dials out to the relay and keeps that connection open. That is why a machine can be reachable from behind NAT or a restrictive firewall without opening an inbound port.

Can the agent use Claude Code or Codex?

Yes. Cmdop can drive a locally installed Claude Code or Codex CLI as the execution engine for a session. Those CLIs use their own local accounts; Cmdop does not collect their account credentials.

Last updated on