Conversation context
A Cmdop session’s context — its machine, its execution engine, its project scope, and its history — lives on the machine rather than in your browser. That is why the same session looks identical from a laptop this morning and a phone this evening, and why changing the scope changes it for everyone attached.
A Cmdop session carries everything needed to keep working on one machine: which machine it is bound to, which execution engine it uses, the project scope you selected, and its durable history.
That context is single-homed on the joined machine. It is not something your browser holds and re-supplies on every visit, which is why the same session looks the same from a laptop this morning and a phone this evening.
What this means in practice
- Switching browsers, devices, or networks does not change the session.
- Reopening a session shows what actually happened while you were away, including work that finished with nobody watching.
- Changing the project scope or the engine changes the session for everyone attached to it, because there is one session, not one per viewer.
Common questions
Where does Cmdop conversation context live?
Cmdop conversation context lives on the joined machine that owns the session, not in the browser tab you used to open it.
Can I resume the same session from another device?
Yes. Because the session context is machine-owned, you can resume it from a different browser, phone, or network and see the same durable history.
Does each viewer get a private copy of the session?
No. A session has one machine-owned context. If one operator changes the project scope or execution engine, everyone attached is looking at that same session.
Cmdop