Work with files on a machine
Cmdop has no separate file browser. You read, edit, and search a machine’s files by asking for it inside a session on that machine, scoped by a Project Root and bounded by that machine’s permission policy. Most people come here after looking for a file tree in the console and not finding one.
Files belong to the machine. You reach them through a session on that machine rather than through a separate browser file tree.
Open the machine in the web console, set a Project Root if the work is scoped to a repository, and ask for what you need — read a file, change one, search across the tree. What the agent may touch is governed by that machine’s permission policy, including which OS-level directories it has been granted. See Permissions.
Chat attachments cached on the relay are listed read-only under Server → Files, with preview and download.
Related
Common questions
Where is the file browser in Cmdop?
File work is reached through the machine, not through a separate global browser tree. Open a machine session, choose a Project Root when relevant, and ask the agent to read, change, or search files.
Do file operations use the machine’s permissions?
Yes. What the agent may touch is governed by the machine’s permission policy and the operating-system permissions of the user running Cmdop on that machine.
What is Server → Files?
It is the relay’s read-only view of cached chat attachments. It is not a general file manager for every machine in the fleet.
Cmdop