Files on a machine
Browse a machine’s files from its web console — open it with
cmdop open. There is no separate top-level files command in the
CLI.
From the terminal, the file operations you have are the ones an agent runs on
your behalf in a conversation (cmdop chat,
cmdop fleet) and, on this host’s own relay scope,
cmdop connect exec.
Where a host-local mounted location is supported, it is created on the computer running the relay console; other clients continue to use the browser file experience. See the console and host documentation for availability and permissions.
Why there is no top-level files command
Cmdop keeps file browsing in the machine workspace because file access is tied
to conversation context, permissions, and the machine that owns the filesystem.
The CLI can open the console and can ask an agent to read or change files, but
it does not publish a separate cmdop files command as a stable cross-machine
API.
For scripts, prefer SDK file APIs or an agent-reviewed command path rather than scraping console file URLs.
Cmdop