Review and change files
Reading a machine’s files has three surfaces — the console, a mounted volume, and read-only fleet tools. Writing has none of those: there is no typed file-write API today, so changes go through a conversation with the machine’s agent, where you ask for one bounded edit and review the diff before accepting it. That review step is the point.
Reading and writing take different paths in Cmdop today, and it is worth being blunt about which is which.
Reading
| Surface | What you get |
|---|---|
| Console Files | Browse, preview, and download. See Browse files. |
| A mounted machine | The machine’s Home directory in your own file manager. See Mount a machine. |
| Fleet tools in an assistant | read_file and list_dir — read-only, one file or one directory per call. See Fleet tools. |
Changing
There is no typed file-write API today: neither the SDK nor the fleet tool set exposes one, and the console’s file tree is a browser surface rather than a published write endpoint. File changes go through a conversation with the machine’s agent, which is where review happens.
For a change that belongs to a project:
- Select the machine that owns the file.
- Choose the relevant Project Root.
- Ask the agent for one specific, bounded change.
- Review the resulting file or diff before you continue.
- Accept it through the project’s normal tests and version control.
Example request:
In this Project Root, update the deployment README to match the current service commands. Show me the diff and do not change source code.
Editing a file through a mounted machine works the same way it does for any network volume — your local editor writes to it directly, and none of the review steps above apply. Use that when you are the reviewer.
Host safeguards remain in force either way: an agent request does not override the operating system’s file permissions, the machine’s permission policy, or your repository’s review rules.
Common questions
Can Cmdop read files on another machine?
Yes. Use browser Files to browse and download, mount the machine to use your local editor, or use fleet tools for read-only assistant access to one file or directory at a time.
Is there a Cmdop file-write API?
No. File changes go through a reviewed conversation with the machine’s agent or through a mounted machine that you edit directly. The SDK and fleet tools do not publish a typed file-write API today.
Do file changes bypass host permissions?
No. Operating-system permissions, Cmdop permission policy, and repository review rules still apply. Asking an agent to edit a file does not override the host’s normal safeguards.
Cmdop