How people use it
A day in Cmdop is one small loop: pick a machine, open or resume a session, optionally scope it to a project folder, choose an execution engine, and ask for the work. Because the session lives on the machine, “continue later” can mean an hour or a week later, from a different device, with the history still there.
The loop is deliberately small.
- Select a joined machine.
- Start a session, or resume one you left.
- Set a Project Root if the work needs repository scope.
- Choose an execution engine.
- Ask for the work, read the result, and continue later.
Step 5 is where the model earns its keep: “later” can be an hour or a week, from a different device, and the session is still there.
Three shapes this takes
Exploratory work. Open a session on a machine you rarely touch, ask what is on it, poke around. No project scope, no setup — the machine already has everything.
Maintenance. Ask for something long-running, close the browser, come back to the finished result in the same session. Or schedule it: ask in an ordinary conversation for the work to happen later or on a cadence, and the machine runs it as a fresh turn when the time comes.
Project work. Scope a session to a repository, pick the engine you prefer, and keep that session as the thread for that project. Reopening it restores the scope and the history together.
Doing this across several machines
One session is bound to one machine. When you want an assistant to move between machines, register Cmdop with it and let it work at fleet level — see MCP integration.
Common questions
What does a normal Cmdop workflow look like?
A normal workflow is: choose a joined machine, open or resume a session, set a Project Root when needed, choose an execution engine, and ask for the work.
Can Cmdop continue work after I close the browser?
Yes. Long-running work belongs to the machine session, so closing the browser does not erase the session or its history.
How does an assistant work across several machines?
One browser session is bound to one machine. For fleet-level work, expose Cmdop through MCP so the assistant can choose the right machine for each task.
Cmdop