Architecture

Cmdop is built from three parts: a machine running the cmdop agent, a relay the agent dials outward to, and a browser workspace you attach from. Execution state is single-homed on the machine, so the session survives your disconnect and you can reattach later from any device without moving anything.

Cmdop is a machine workspace, not an administration dashboard. You open a browser conversation bound to one joined computer, optionally scope it to a project folder, and choose an execution engine. Work happens on that machine.

The pieces

• The machine owns its files, its tools, and the authority to execute.
• The session is the durable work thread for that machine. It lives on the machine, not in your browser tab.
• The machine workspace is the browser surface where you select context, ask for work, and read results.
• The relay is what machines dial into so the workspace can reach them, and what serves the embedded web console.
• Execution engines are CMDOP itself or a supported coding-agent CLI you already have installed.

Properties you can rely on

• Execution state is single-homed. One machine holds it. Operators are distributed; the state is not.
• The session survives disconnect. Close the tab, lose the network, come back tomorrow — the session is still there and still on the same machine. The agent makes an outbound connection to its relay and keeps it open; nothing dials in, so no inbound port has to be opened on the machine.
• Operators attach, detach, and reattach. A person, an AI, a device, or a service joins an existing live session rather than starting a private copy of it.
• The session is ownerless. No operator is a privileged occupant of it.
• You observe live state, not a replay. What you see is the session as it is, not a transcript reconstructed after the fact.
• The session is transport-independent. How you reached it is not part of what it is.

Where to go next

Common questions

What is Cmdop’s architecture in one sentence?

Cmdop is a joined machine, an outbound relay connection, and a browser workspace attached to a durable session. The machine owns execution state; the relay provides reachability; operators attach from clients.

Why does the session survive disconnect?

The session lives on the joined machine, not in the browser tab. Closing a tab or losing the network detaches one operator; it does not move or erase the machine-owned session.

Is the browser workspace where commands run?

No. The browser workspace is an attachment surface. Commands and tools run on the selected joined machine, under that machine’s engine, files, permissions, and credentials.