Execution context
Cmdop makes you choose three things before it runs anything: which machine, an optional Project Root to scope the work to, and which execution engine does it. That context belongs to the session on the machine, so it is the same for every operator attached and it survives your disconnect.
Before you ask for work, Cmdop shows you where it will happen: the selected machine, the optional Project Root, and the execution engine. Nothing about that is implicit, because “run this” means something different on your laptop than on a build box.
The three choices
| What you pick | What it decides |
|---|---|
| Machine | Which computer’s files, tools, and network the work uses. |
| Project Root | The folder the work is scoped to, when it needs repository scope. |
| Execution engine | Which agent runtime does the work — CMDOP or a supported coding-agent CLI you already have installed. |
The context belongs to the session on the machine, so it is the same for every operator attached to that session and it survives your disconnect. Changing it changes it for the session, not just for your view of it.
Related
Common questions
What is execution context in Cmdop?
Execution context is the selected machine, optional Project Root, and execution engine for a session. It tells every operator where work will happen before a request runs.
Does changing context only affect my browser?
No. Context belongs to the session on the machine. Changing it affects that live session for every attached operator.
Why choose a Project Root?
Choose a Project Root when the task needs repository scope. It lets the machine resolve paths and review changes relative to the intended project.
Cmdop