Execution engines
An execution engine is what performs the work behind a Cmdop conversation. There are three: Cmdop’s built-in CMDOP engine, plus the locally installed Claude Code and Codex CLIs, which Cmdop detects and drives. You pick one when a session starts and it stays bound for that session’s life, so past work remains attributable to the engine that did it.
An execution engine is the thing that actually does the work in a session. Cmdop supports three: its own built-in CMDOP engine, and the locally installed Claude Code and Codex CLIs, which it detects and drives.
They are not three separate products with three separate histories. They share one machine model, one project model, and one conversation history per machine.
Chosen per session, bound for its life
A session keeps the engine it started with. That is deliberate: a past piece of work stays attributable to the engine that performed it, and a restored session cannot have its meaning rewritten by a later UI selection. To use a different engine, start a new conversation.
| Engine | Where inference comes from | Account |
|---|---|---|
| CMDOP | The CMDOP Router | Your platform API key |
| Claude Code | The local Claude Code CLI | That CLI’s own sign-in |
| Codex | The local Codex CLI | That CLI’s own sign-in |
Cmdop drives the external CLIs; it does not collect, store, or manage their account credentials.
Project scope applies to all three
Project scope is not a driven-engine feature. Every engine works against the same Project Root you selected for the conversation, resolved by the machine that owns the folder. Cmdop supplies the same repository-instruction layer to the driven engines, so a project does not behave materially differently just because you chose Claude Code over Codex.
Engine and model are different choices
The engine decides what performs the work. The model decides how that engine reasons. Choosing a model never changes the machine, the project, or the session’s identity. For CMDOP, the model can be selected per turn; for the driven engines, the model binds when the session begins along with the engine.
Common questions
What is a Cmdop execution engine?
A Cmdop execution engine is the worker behind a conversation. It may be the built-in CMDOP engine or a local CLI engine such as Claude Code or Codex.
Can one session switch from Claude Code to Codex?
No. The engine is selected when the session starts and stays bound for that session. Start a new conversation to use a different engine.
Is the model the same thing as the engine?
No. The engine performs the work; the model is the reasoning choice available inside that engine. Changing a model does not change the machine or session.
Cmdop