Get started
Getting started with CMDOP takes three steps on the computer you want an AI
employee to work on: install the cmdop binary, join that machine to a fleet
with a join key, and run cmdop to open its browser console. From there you
hire a worker by assigning it a role, hold a durable conversation with it,
optionally bind the work to a project folder, and pick which execution engine
runs the work.
CMDOP is a machine workspace. Its primary experience is a browser conversation with a joined computer, an optional project folder, and an execution engine. Start with the result you want to produce; the operational surfaces stay in the background until you need them.
Start here
- Install the
cmdopbinary on the machine that will do the work:curl -fsSL https://install.cmdop.com | sh - Join that machine to its fleet with the fleet join key, then start it.
- Run
cmdopto open your door — the web console on a desktop computer, the terminal chat on a headless host — and start or resume a conversation. - Choose a Project Root when the work belongs to a repository.
- Hire a worker by assigning it a role, or use CMDOP, Claude Code, or Codex directly for the conversation; review the result and return to the same durable history when the work continues.
The web console is the primary client. The terminal is a full second door, not a
fallback: cmdop chat reaches the same conversation from a shell or over SSH.
Join a machine, open its console, and begin a conversation.
What is CMDOP?The product model and the boundaries between workspaces, operations, and integrations.
Concepts: roles and agentsHow a role gives a machine a persistent persona, and how it differs from a Skill.
Install the CLIInstall the single binary on a workstation or server.
Run commands without opening portsHow the outbound relay model reaches joined machines behind NAT or a firewall.
Give an AI assistant a fleetLet Claude Code or Codex list machines and work across them through Cmdop.
Run on a server without SSHOperate a joined server without exposing an SSH daemon to the internet.
CLI referenceUse Cmdop from a terminal or manage a joined machine.
Go deeper when you need to
- How CMDOP works explains the machine, conversation, project, and engine model.
- Let an AI agent reach a machine behind NAT covers remote assistant access with no port forwarding and no VPN.
- Where Cmdop fits compares Cmdop with SSH, ngrok, Cloudflare Tunnel, Tailscale, and Claude Code Remote Control.
- System overview explains the browser console, the local relay, and the supporting platform services.
- Connect covers interactive terminal access to another joined machine and the current boundary of one-shot execution.
Where you can use it
The cmdop binary runs on macOS, Linux, and Windows. On macOS and Windows a
menu-bar tray comes with it. Native iOS
support is planned for a later release and is not
currently in production.
Common questions
How do I get started with Cmdop?
Install the cmdop binary on the machine that will do the work, join it to a
fleet with a join key, then run cmdop to open the console or terminal chat.
What should I read first?
Start with Quickstart for a first machine, then read How CMDOP works for the machine/session model and Connect when you need remote terminal access.
Can I use Cmdop without opening ports?
Yes. A joined machine dials out to its relay, so the getting-started path does not require opening an inbound port on the machine.