Remote terminal sessions
A terminal session opened with cmdop connect <machine> lives on the target
machine, not in your terminal emulator. That single fact explains most of how it
behaves.
Detach, reattach
- Losing your connection detaches you. It does not kill what is running. The work continues on the machine that owns it.
- Reattaching returns you to the same session, with live state — not to a fresh shell, and not to a replay of what you missed.
- The session is transport-independent. Which network you came in on is not part of the session’s identity, so reconnecting from somewhere else is the same operation.
Two terminal outcomes, different reach
| Command | Reach |
|---|---|
cmdop connect <machine> | Machines reachable at their own relay door; authenticates there, plus that machine’s connection PIN when armed |
cmdop connect exec <machine> -- <cmd> | This host only — no path to another machine’s public door |
A machine on a LAN-only relay can be worked with through the console but cannot be attached to remotely. See Interactive attach for the full precondition list and One-shot execution for the narrower path and its 30-second default timeout.
Not yet: interactive takeover
Taking over another operator’s live interactive terminal is not something Cmdop offers today. Plan around attaching and reattaching to your own sessions, not around seizing someone else’s.
Common questions
Does disconnecting from a Cmdop terminal kill the work?
No. Losing your connection detaches you. The terminal session continues on the target machine that owns it.
What happens when I reattach to a remote terminal?
Reattaching returns you to the same target-machine session with live state, not to a fresh shell or transcript replay.
Can I take over someone else’s interactive terminal?
No. Cmdop does not currently offer interactive takeover of another operator’s live terminal.
Related
- Remote work — why any of this reaches.
- Conversations and sessions
Cmdop