Durable conversations
A Cmdop session survives disconnect. Close the browser, lose the network, or come back a week later on a different device, and you reattach to the same session with its machine, project scope, engine, and history intact — including work that finished while nobody was watching. Leaving does not end the work.
A Cmdop session is a durable work thread on a machine, not a browser window that happens to contain some text. The session survives disconnect.
Close the tab, put the laptop to sleep, switch from office Wi-Fi to a phone hotspot, come back the next morning: you reattach to the same session and it still has its machine, its project scope, its engine, and its history. Work that ran while you were gone is there when you return.
Why it works that way
The session is single-homed on the joined machine, and the machine’s agent makes an outbound connection to the relay and keeps it open; nothing dials in. That is why a joined machine works from behind NAT or a firewall with no port forwarding and no VPN. Your browser attaches to that session; it never became the session.
That also makes it transport-independent: how you reached the session — LAN, public relay edge, your own domain — is not part of what the session is, so changing it does not restart anything.
What still depends on the machine
Reattaching gets you the session. It does not conjure a machine that is powered
off, an engine that is not installed, or a permission you were not granted. If
a session looks stuck, check the machine first with cmdop status — see
Connection issues.
Common questions
Does closing the browser stop a Cmdop session?
No. Closing the browser detaches your view from the session. The session itself belongs to the joined machine and can still be reattached later.
Can I return to work that finished while I was away?
Yes. Reattaching returns to the live machine-owned session, including history and work that completed while no client was watching.
Why does this work across different networks?
The transport you used to reach the session is not part of the session. The machine’s agent maintains its outbound relay connection, and operators attach to that machine-owned state from whatever supported client they are using.
Cmdop