AI in the workspace

In Cmdop the AI is an operator, not a controller: it attaches to the same live session on the same machine you are attached to, and works there while you stay present. You are not locked out during a run, you see the same live state it sees, and you can steer mid-flight instead of only accepting a finished result.

AI assistance is not a separate mode in Cmdop. The model attaches to the same live session on the same machine that you are attached to, and it works there while you are present.

AI as operator, not controller

The distinction is the point of the product.

A controller takes the wheel: you describe a goal, hand over the system, and watch a result arrive. If it goes wrong, your options are to stop it and start over.

An operator works alongside other operators in a shared live session. That means:

• You stay attached while it works. You are not locked out for the duration of a run, and you do not have to wait for a turn to end to see where things stand.
• You see the same state it sees, live — not a summary of what it did, and not a replay assembled afterwards.
• You can steer mid-flight rather than only accepting or rejecting a finished result.
• The AI observes the effects of its own work in the same session, so the next step is taken against what actually happened, not against what was predicted to happen.
• It has no privileged occupancy. The session is ownerless: the AI being attached does not evict you or subordinate you.

What the AI may do is a separate question from where it may be present. That is decided by permissions, which apply to the AI’s actions the same way they apply to any other tool activity on the machine.

Getting work done

The everyday loop is the ordinary one: choose a machine, set project scope when the work belongs to a repository, choose an execution engine, and ask for the outcome in plain language. The workspace shows the active machine, project, and engine before work begins, so you can see where it will happen.

Available capabilities depend on the machine, the selected engine, and the permission policy configured for that machine.

Common questions

What does AI as operator mean?

AI as operator means the model works inside the same live machine session as you. It does not take exclusive control of the machine or hide the live state.

Can I steer the AI while it works?

Yes. Cmdop is built around a shared session, so you can stay attached, observe progress, and steer the work while it is running.

Do AI actions bypass permissions?

No. AI actions are still governed by the machine’s permission policy and the capabilities available to the selected execution engine.

Related

• Conversations and sessions
• Permissions
• Execution engines
• AI as Operator, Not Controller — the deeper treatment.