Workspace clients
Cmdop’s ways in — the web console, terminal chat, the menu-bar tray, a remote terminal, the SDK, and MCP clients — are not separate products with separate state. Each attaches to the same live session on the same machine as an operator, so switching between them is not a handover and none locks the others out.
Cmdop has several ways in, and they are not separate products with separate state. Each one is a client that attaches to the same live session on the same machine.
Client surfaces
| Client | What it is for |
|---|---|
| Web console | The primary machine workspace: conversations, files, settings. |
Terminal chat (cmdop chat) | The same conversation from a shell, including over SSH. |
| Menu-bar tray | Status and quick controls on a macOS or Windows desktop. |
Remote terminal (cmdop connect) | An interactive terminal on another joined machine. |
| SDK | Your own code working against a relay. |
| MCP clients | An external AI client reaching your fleet through Cmdop. |
Operators, not owners
Everything attached to a live session is an operator — a browser tab, a terminal, a phone, a service, or the AI itself. This is one role, not a hierarchy of client types.
Because the session is single-homed on the machine, operators do not each hold their own copy of the work to reconcile later. They attach to the live state and detach from it. A session is ownerless: an operator being present does not lock the others out.
Two consequences worth planning around:
- Switching clients is not a handover. Move from the browser to the terminal and you are looking at the same session, not restarting it somewhere else.
- The AI is one of the operators. It works in the same session you are in, under the same permission boundary — see AI in the workspace.
Each client authenticates on its own terms
A client being able to render your workspace does not make its credential transferable. The browser console, the SDK, a joined machine, and a remote terminal attach each authenticate separately, and their credentials are not interchangeable. See Identity and access and the security model.
Related
Common questions
Can I switch between browser, terminal, SDK, and MCP?
Yes. These are clients attached to the same machine-owned session. Switching clients is not a handover and does not move the work.
Does one client own the session?
No. Clients are operators, not owners. A browser tab, terminal, service, or AI assistant can attach without locking the others out.
Do all clients use the same credential?
No. The browser console, SDK, joined machine, and remote terminal attach each authenticate on their own terms. Their credentials are not interchangeable.
Cmdop