Remote machines
Cmdop separates four actions:
| Goal | Command |
|---|---|
| Make this machine available | cmdop start |
| See what machines you have | cmdop machines |
| Open a terminal on another machine | cmdop connect <machine> |
| Run one command through this host’s embedded relay | cmdop connect exec <machine> -- <command> |
Start by joining this machine. For cross-host terminal access, the target must be joined to the fleet, running, and reachable through its configured remote-terminal address.
The current one-shot connect exec path is self/loopback scoped and must not be
treated as the non-interactive equivalent of cross-host terminal attach.
To talk to another machine’s agent rather than attaching a terminal, use
cmdop fleet.
Remote does not always mean terminal
Use a terminal when you need direct interactive control. Use cmdop fleet when
you want the other machine’s agent to interpret a task, use tools, and report
back. Use cmdop machines when you only need inventory. Keeping those jobs
separate avoids treating every remote-machine action as a shell session.