Working on one machine together
People, AI, devices, and services attach to the same live Cmdop session as operators, and every one of them observes the same live state as it happens. The session is ownerless: attaching evicts nobody, detaching ends nothing, and an AI working there is one operator among the rest, not the owner.
A Cmdop session is not a private window. Humans, AI, devices, and services all attach to the same live execution as operators.
This is the product’s central idea: AI as operator, not controller. An agent working in a session is one operator among the others. It does not take the session over, and you do not have to hand it away to let it work.
What an operator sees
Every operator attached to a session observes the same live state. When someone — or something — does work, the others see it happen, not a summary of it afterward.
Because the session is ownerless, no operator holds it against the rest. Attaching does not evict anyone; detaching does not end the work. You can leave an agent running and come back to watch it.
What an operator can do
Which surfaces you can attach from, and which actions are available once you have, depend on the surface you are using and the permissions configured for that machine. See Permissions.
Common questions
What does AI as operator mean?
It means the AI attaches to the same live machine session as a participant. It can observe and act through the available tools, but it does not own the session, evict other operators, or move the work away from the machine.
Can a person and an AI work in the same session?
Yes. People, AI, devices, and services can attach to the same live session and observe the same state. Detaching one operator does not end the work for the others.
Do operators see a replay or live state?
They see live session state. Cmdop is not reconstructing a transcript as a substitute for the session; operators attach to the machine-owned work as it is.
Cmdop