What Cmdop is not
Cmdop is not an administration dashboard, not a cloud coding environment, not a marketplace, and not a replay tool. It connects you to a computer you already own — your files, your tools, your network — through a live session you attach to, and it composes the coding-agent CLIs and MCP servers around it rather than replacing them.
Cmdop is a machine workspace — the command-operator execution layer. Naming what it is not is the fastest way to place it.
Not an administration dashboard. The primary experience is a browser session bound to a real joined machine, not a fleet inventory you look at. There is a console, and it does real work — but the console exists to serve the session, not the other way round.
Not a cloud coding environment. Cmdop does not give you a rented container to work in. It connects you to a computer you already have, with your files, your tools, and your network.
Not a marketplace. The catalogue is discovery. Installation, approval, and runtime state belong to the machine — see Marketplace and installed state.
Not a replacement for the tools around the machine. Coding-agent CLIs, MCP servers, and Skills keep their own boundaries, their own accounts, and their own lifecycles. Cmdop composes them; it does not absorb them.
Not a replay tool. Operators watch live state, not a log reconstructed after the fact.
Related
Common questions
Is Cmdop a cloud IDE?
No. Cmdop connects you to a computer you already have, with that machine’s files, tools, and network. It does not rent you a hosted coding container.
Is Cmdop just an administration dashboard?
No. The console exists to serve a live machine-bound session. Inventory and status matter, but the primary product is working in a session on a real joined machine.
Is Cmdop a marketplace?
No. Marketplace discovery is one supporting surface. Installation, approval, and runtime state belong to each machine.
Cmdop