Mount a machine in your file manager

Mounting lets you work on a remote machine’s files with your own editors and tools, because its Home directory appears as an ordinary volume on your desktop instead of something you copy from. Run the console on the computer where the volume should appear and mount from there: only that computer can change its own desktop session, so the action is unavailable from a console opened remotely.

Cmdop can open one joined machine as a native location in your own file manager — a Finder volume on macOS, a network location in Linux Files, or a drive letter in Windows Explorer. Your normal editors and tools then open that machine’s files directly, with no upload or download step.

The volume shows the machine’s approved Home directory. It is not the machine’s filesystem root, and mounting one machine never mounts the others.

Before you start

Run cmdop status on the target machine and confirm it has joined the relay and is online.
Open the console on the computer where you want the volume to appear, and sign in there as the local operator.
Check that native mounting is available on that computer:


cmdop doctor

The Native volumes line reports either the backend it will use or a stable reason it cannot. Run it in the same signed-in desktop session as the console — a background service session is not the same thing.

If you opened the console from another computer, the mount action is intentionally unavailable: only the computer running the console can change its own desktop session. Browser Files still works from anywhere.

Mount a machine

Open Machines in the console.
Select the machine, then open Files.
Under Use as a local drive, select Mount on this computer.
When the state reads Mounted, select Open in file manager.

Unmount it

Open the volume-actions menu next to the mount and select Unmount from this computer. The operation is safe to repeat.

If the unmount reports that the volume is busy, close the files and applications using it and retry. Use Force unmount only after reading its confirmation — open files can lose unsaved changes.

Read the state

State	What it means
Mounting / Unmounting	The operating system is still changing the location. Wait for it to settle.
Mounted	The volume is available in your file manager.
Waiting to reconnect	The mount still exists, but the machine is currently offline. It resumes when the machine returns.
Needs attention	The last operation failed. The state names the reason; resolve it and retry.
Native mounting unavailable	This computer or desktop session lacks a required capability. Use browser Files.

Platform notes

Platform	What you get	Requirements
macOS	A Finder volume named after the machine.	Built in — nothing to install.
Linux	A network location in your file manager. It may show a provider label or URI instead of the machine name, and may not have a conventional local path.	`gio`, a running desktop session, and the GVfs WebDAV backend. Cmdop reports a missing prerequisite but never installs system packages for you.
Windows	A temporary drive letter.	An interactive signed-in session and the Windows WebDAV Redirector. If no letter from `D:` to `Z:` is free, disconnect a mapped drive and retry.

When to use which surface

You want to	Use
Open machine files in your local editor and tools	This page — mount the machine.
Look at or download one file from anywhere	Browse files in the console.
Let an assistant read files across the fleet	Fleet tools.

Common questions

How do I mount a remote machine as a local drive?

Open the console on the computer where the volume should appear, select the joined machine, open Files, and choose Mount on this computer. Cmdop mounts that machine’s approved Home directory into your local file manager.

Why is the mount button unavailable?

Mounting changes the desktop session of the computer running the console. If you opened the console from another computer, use browser Files instead, or open the console locally where the volume should appear.

Does mounting one machine mount the whole fleet?

No. Mounting is one machine at a time and exposes that machine’s approved Home directory, not its filesystem root and not other machines.