Files on a machine
Attach a fleet machine’s files as a real volume in your file manager with
cmdop mount <machine>. The volume appears like any other disk — drag files
in and out, open them in any application — and you release it with
cmdop unmount <machine>.
cmdop mount workstation
cmdop mount workstation --open
cmdop mount workstation --startup --read-only| Flag | Effect |
|---|---|
--open | Reveal the volume in the file manager once it is mounted. |
--read-only | Mount without write access. |
--startup | Re-mount this machine automatically at login. |
cmdop unmount workstation
cmdop unmount workstation --force # unmount even if reported busy
cmdop mounts # list machine volumes and their stateUnmounting a machine that is not currently mounted is not an error, so
cmdop unmount is safe to run defensively before re-mounting or shutting
down. cmdop mounts lists every machine you currently have mounted and
whether each volume is healthy, read-only, or configured to remount at
startup — use it to check state before assuming a mount succeeded silently.
The mounted volume is a real filesystem entry on the computer running
cmdop mount, backed by the machine’s own files over the relay connection —
not a synced copy, so changes on either side are visible without a transfer
step. It is the fastest way to work on a remote machine’s files with your
normal local tools (an editor, a build, a search index) rather than through
the browser or a conversation.
You can also browse a machine’s files from its web console — open it with
cmdop open — and, from the terminal, ask an agent to read or
change files in a conversation (cmdop chat,
cmdop fleet) or run
cmdop connect exec on this host’s own relay scope.