System overview

CMDOP puts the work on the machine and the clients everywhere else. Each joined machine holds its own files, conversations, and execution authority, and serves a web console from a relay built into the same binary. Browsers, terminals, the menu-bar tray, and AI attach to that machine as operators; none of them owns the state they act on.

CMDOP’s primary client is the web console served by a joined machine’s own relay. The machine holds the work; the console, the terminal, and the tray are clients that attach to it.

Product boundaries

Part	Role
CMDOP platform	Account, entitlements, and inference policy.
Router	Model selection and inference for CMDOP’s built-in engine.
Joined machine	Files, tools, Project Roots, durable conversation context, live sessions, and execution authority.
Embedded relay	Serves the web console, connects the machine to its fleet, and runs machine-local operational services.
Web console	The primary machine-workspace client.
Terminal chat and menu-bar tray	The other first-party clients on the same machine.
Claude Code and Codex	Locally installed external execution engines that work in the same machine and project model.

Two properties that shape the whole picture

The machine dials out. An agent makes an outbound connection to its relay and keeps it open; nothing dials in. That is why a joined machine works from behind NAT, and why “online” means “its connection is live” rather than “a port is open”.
Execution state is single-homed. One machine owns the state for its work. Operators — browsers, terminals, services, the AI — are distributed across wherever people happen to be; the state they act on is not.

A user’s path through the system


joined machine
  → durable conversation
  → optional Project Root
  → CMDOP, Claude Code, or Codex
  → results and continued work

The console displays this model and requests explicit actions. It does not own machine filesystem paths, durable session bindings, or capability permissions.

Supporting capabilities

Relay operation, public reachability, Skills, external MCP tools, and fleet MCP are distinct supporting surfaces. They have separate setup and approval boundaries, so they should not be treated as one generic integration feature.

Learn more

Common questions

Where does Cmdop keep execution state?

Execution state is single-homed on the joined machine. Browsers, terminals, tray controls, services, and AI operators attach to that state; they do not own separate copies of it.

Why does Cmdop work behind NAT?

The agent on a joined machine dials out to its relay and keeps that connection open. Nothing has to dial into the machine for the normal workspace path.

Are Skills, MCP, and relay operation one integration feature?

No. Relay operation, public reachability, Skills, external MCP tools, and fleet MCP are separate supporting surfaces with separate setup and approval boundaries.