Session history
A Cmdop session lives on the machine it runs on, not in the browser tab you opened it from. That is why you can close the tab, come back later from anywhere, and find the session with its project scope, execution engine, and full history intact — including work that finished while nothing was attached.
A session belongs to the machine it runs on, not to the browser you opened it from. That is why you can close the tab and come back to it — see Durable conversations.
Getting back into one
Open the web console, select the machine, and pick the session. Its project scope, execution engine, and full history come back with it, including work that completed while nothing was attached.
Everything a session did that produced a reply is in that history. Reopening a conversation after a scheduled task fired shows the task’s result in place.
Attaching from elsewhere
You are one operator among several. An assistant registered through MCP, the CLI, and another browser can all be attached to the same live session — they see the same state, not private copies of it. See Working on one machine together.
Common questions
Where do Cmdop sessions live?
Cmdop sessions live on the machine that runs the work, not in the browser tab that opened them.
How do I reopen a Cmdop session?
Open the web console, select the machine, and pick the session. Its project scope, execution engine, and history come back with it.
Can multiple operators attach to one session?
Yes. A browser, CLI, and assistant registered through MCP can attach to the same live session and see the same state.
Cmdop