Give an assistant fleet access
Cmdop exposes fleet operations to a locally installed Claude Code or Codex
session through MCP, so you can say “list my machines”, “ask web-01 what is
using its disk”, or “run df -h on the build box” inside the assistant.
These tools reach other machines across the relay. They are not a local shell — the assistant already has its own shell and file tools for the machine it runs on.
1. Prepare the machine you work from
Complete the Quickstart and confirm that at least one target
machine is online. The machine you work from must have joined a relay: the fleet
tools use the same relay credential that cmdop join stored, so a machine that
has not joined one gets a clear “not logged in” reply from every tool rather
than a failure.
2. Register the assistant
For Claude Code, this is automatic. When Claude Code is installed, the Cmdop
agent registers the cmdop-fleet plugin on start — you do not run any command.
It works in either order: install Cmdop first and Claude Code later, or the
reverse. Restart Claude Code afterwards so it picks the tools up.
Codex is explicit opt-in:
cmdop mcp install --agent codex
cmdop mcp statusTo register immediately rather than waiting for the next agent start, or to check what is registered where:
cmdop mcp install # register now, both assistants
cmdop mcp status # registration state for Claude Code and Codex
cmdop mcp tools # list the fleet tools Cmdop exposesinstall and uninstall take --agent all|claude|codex, defaulting to all.
Cmdop registers its own local MCP server; it never takes ownership of the
assistant’s account credentials.
3. Know what the assistant can do
The fleet plugin gives the assistant two things: the tools, and three bundled fleet skills — diagnose, rollout, and orchestrator — that shape how the assistant sequences those tools for common jobs. Claude Code always gets both; Codex gets the skills too when its installed version supports plugins, and the tools either way.
The three you will use first:
| Tool | What it does |
|---|---|
list_machines | Lists your fleet with each machine’s online status and OS. |
ask_machine | Sends a natural-language task to a machine’s own agent and returns its reply. |
run_command | Runs one shell command on a machine and returns its output and exit code. A non-zero exit is a result, not an error. |
Five more cover files and machine health — read_file, list_dir,
care_status, care_diagnose, and care_storage_inventory. All eight, with
how a target is resolved, are on
Fleet MCP tools.
The practical habit: ask the assistant to list machines first, then name the
exact target. A known machine can still be offline or require its own connection
PIN, which is passed as an argument to ask_machine and run_command.
4. Work across several machines
There is a fleet orchestrator you can address: list_machines includes a
synthetic server host, and asking it routes the request to the orchestrator
rather than to one machine’s agent. The bundled orchestrator skill uses it for
exactly this.
What Cmdop does not give you is an atomic multi-machine transaction or an automatic merge of several machines’ results. So when the work spans machines, keep the orchestration explicit:
- List the online machines first; do not target every discovered machine by default.
- Submit one bounded task per machine, or hand the whole job to the orchestrator host — not both for the same work.
- Keep each machine’s reply, PIN, timeout, and error separate.
- Combine results only after you have validated each one individually.
- Start sequentially. Add concurrency only when the tasks are independent and you can identify a partial completion.
Never reuse one machine’s credential against another target.
5. Remove access when finished
cmdop mcp uninstall --agent codex
cmdop mcp statusFor the full registration workflow and per-client details, see Claude Code and Codex.
Common questions
How do I give Claude Code access to my Cmdop fleet?
Install Cmdop on the machine where Claude Code runs and make sure it has joined the relay. Cmdop registers the fleet plugin for Claude Code on agent start; then restart Claude Code and ask it to list machines before targeting one.
How do I give Codex access to my Cmdop fleet?
Run cmdop mcp install --agent codex, restart Codex, and ask it to list
machines. Codex receives the fleet tools through MCP; when its installed
version supports plugins, it also receives the bundled fleet skills.
Can an assistant work across several machines at once?
Yes, but keep orchestration explicit. List online machines first, target one machine or the fleet orchestrator for each bounded job, and keep each machine’s reply, PIN, timeout, and error separate.
Cmdop