What is CMDOP?

CMDOP is an AI agent that lives on every machine you own and lets you operate the whole fleet from one prompt. The agent runs locally; the desktop and CLI are just front doors to it; remote machines reach each other through an outbound-only relay called Connect.

The thirty-second pitch

You have a laptop, a Mac Studio in the office, and a VPS like vps-audi somewhere in a datacenter. After installing CMDOP on each:

The desktop client on the laptop chats with a local agent for everyday work.
The same chat can call the agent on vps-audi to read logs, restart services, or open issues.
A single prompt can fan out to many machines at once and aggregate the answers.
A skill (a small reusable bundle) wraps a recurring task into one named action.
The same surface is wired into Claude Desktop and Cursor through MCP — no second login.

No inbound ports, no SSH gymnastics, no copying scripts around.

What CMDOP is, concretely

A small Go binary, cmdop, that runs on every machine.
A long-running daemon (cmdop agent start) that keeps the machine “online” against the relay.
A desktop client that wraps the same Go core in a GUI with seven tabs (Chat, Machines, Board, Activity, Connection, Projects, Settings).
A CLI with the same core, made for shells and scripts.
A Connect subsystem — workspaces, machines, share links, agent-to-agent calls.
An MCP server so Claude Desktop and Cursor can call the same tools.
A web cabinet for workspaces, billing, and observability — not where you do work.

What CMDOP is not

It is not an SSH replacement in the literal sense; it does not give you a TTY into a machine you do not own. It is an agent platform that happens to handle remote command execution as one of its tools.
It is not a chatbot bolted on top of ssh. The agent loop, tools, audit log, and permission gate are first-class.
It is not a hosted service that runs your code in the cloud. Your code runs on your machines.
It is not “yet another devops tool”. It is a way to make AI a first-class operator on systems you already own.

Who is this for

A solo developer with a laptop and a couple of servers who wants one prompt to reach all of them.
A small team that wants AI to take real action on their fleet without giving up an audit trail.
An IDE-bound developer who wants Claude Desktop or Cursor to actually run things, not just suggest commands.

If you have a fleet of thousands and a dedicated SRE team, you probably want a different tool. CMDOP is built for individuals and small teams.

What changed recently

If you read older docs, two names will look different.

cmdop ssh was renamed to cmdop connect. The CLI verb, the agent tool, and the docs section all moved. Behavior is the same; the framing is honest — Connect is an agent-to-agent surface, not an SSH wrapper.

The desktop client also became the primary surface. The web cabinet still exists, but for workspaces, billing, observability, and account management — not for everyday operating.