Conversations and sessions

A Cmdop session is live execution on one joined machine; the conversation is the durable thread you see of it and return to. A session is not your browser tab — it is held by the machine owning the files and tools, so execution state is single-homed, the session survives your disconnect, and reattaching shows live state rather than a replay.

A Cmdop session is live execution on one joined machine. The conversation is what you see of it: a durable work thread you can leave and come back to.

The distinction matters because it is what makes the product behave the way it does. The session is not your browser tab, and it is not stored in your browser. It is held by the machine that owns the files, the tools, and the execution authority.

What follows from that

• The session survives your disconnect. Close the tab, lose Wi-Fi, put the laptop to sleep. Work in flight keeps running on the machine. When you come back you reattach to the same session, with its history intact.
• You attach, detach, and reattach. These are ordinary operations, not recovery paths. Attaching is not “starting”; detaching is not “stopping”.
• You see live state, not a replay. When you reattach, you are observing the session as it is now — not watching a reconstruction assembled from a log of what happened while you were away.
• The state is single-homed. One machine owns the execution state for its work. That is what makes reattaching mean something: there is exactly one place the truth lives, so two clients cannot drift into two versions of it.
• A session is ownerless. No operator occupies it in a way that locks others out. You, a colleague’s client, and the AI can all be attached to the same live session. This is about presence, not privilege — what each operator may do is decided by permissions.

Context is bound when the session begins

A session keeps the execution engine it started with. When a project folder matters, choose a Project Root before the first turn.

Changing to a different project starts a new conversation rather than silently changing the working directory under an existing transcript — so past work keeps the meaning it had when it was done. The same rule holds generally: a context change that would alter execution semantics creates a new session instead of mutating a live one.

The workspace always shows the active machine, project context, and engine, so you can see where work will happen before you ask for it.

Related

• Remote work — reaching a session on another machine.
• Conversation history
• Workspace clients
• The Session as a Computational Primitive — the deeper treatment.

Common questions

What is a Cmdop session?

A session is live execution on one joined machine. It owns the current machine, project context, engine, and work in flight; the conversation is the durable thread you return to.

Does closing the browser end the session?

No. Closing a browser tab detaches one client. The session stays on the machine and can be reattached later with its history and live state intact.

Can several operators share one session?

Yes. A person, browser, terminal, program, or AI can attach to the same live session. Permissions decide what each admitted action may do.