Browse files

To inspect another machine’s files, open Machines → Files in the console, select the machine, and navigate from its Home directory, previewing or downloading what you need. The view is deliberately bounded to that Home directory rather than the whole filesystem, and the machine’s own OS permissions still apply on top — so browsing widens nothing.

The console’s Files view is the zero-install path for inspecting a joined machine: open it from any browser you are already signed in on. The machine stays the authority for paths and access — browsing does not turn your own computer’s filesystem into the machine’s.

Browse a machine

1. On the target machine, run cmdop status and confirm that it is online.
2. Open the console with cmdop open, or use your existing authenticated entry point.
3. Open Machines, select the machine, then open Files.
4. Navigate from the machine’s Home directory, which is where the view starts.
5. Select a supported file to preview it, or download it for local inspection.

The view is deliberately bounded to that Home directory: it does not expose the machine’s filesystem root, and a path outside it is not served merely because a browser asked for it. The operating system’s own file permissions still apply on top of that.

Project Root

Several surfaces — Files, conversations, and project review — ask you to choose a Project Root: one directory on one machine that you have designated as the root of a project. It is machine-scoped, so the same repository checked out on two machines is two different Project Roots, and the machine that holds the files is the one that validates and owns the selection. Choosing a Project Root scopes what a conversation reads and changes; leaving it unset does not widen access, it just means no project context is attached.

If a file is missing

• Confirm you selected the right machine, and the right Project Root if the task is project-scoped.
• Check that the file exists for the OS user that runs Cmdop on that machine — a file another user owns may be unreadable.
• Refresh after a reconnect. Do not assume an open browser tree is current.
• Use the machine’s own OS tools when the file needs host administrator access.

Other ways to reach the same files

Common questions

How do I browse files on another machine?

Open the console, select the joined machine, then open Files. The view starts at that machine’s Home directory and lets you preview or download supported files without installing anything on the computer you are sitting at.

Does browser Files expose the whole filesystem?

No. The browser file view is bounded to the machine’s approved Home directory and still respects the operating system permissions of the user running Cmdop.

Why is a file missing from the browser?

Confirm the selected machine and Project Root, refresh after reconnect, and check whether the file is readable by the OS user that runs Cmdop on the target machine.