Skip to Content
DocsConnectMachine-to-machine requests

Machine-to-machine requests

Joined machines in the same fleet can ask each other for work. This is how a task that spans computers gets done without you driving each hop by hand — and it is how an AI agent on one machine delegates to another.

It is a request between agents, not a remote shell. The target machine’s agent does the work in its own context, with its own files and tools, and replies.

The shapes available

  • Ask one machine — a task or question for one named computer.
  • Ask several machines — the same request fanned out, with per-machine results.
  • Ask the fleet orchestrator — addressed as the machine named server, for goals that span the fleet rather than targeting one computer.

From the terminal, cmdop fleet <machine> is the human-facing form of the first. Inside a conversation, the agent reaches other machines the same way, using the tools available to it. An external MCP client can drive the same fleet access — see MCP.

Credentials and gates

A machine uses the fleet membership it already holds; no separate server-to-server credential is minted. Two gates then apply, and they answer different questions:

GateQuestion it answers
Connection PIN on the targetMay this caller drive that machine at all?
Permission policy on the targetWhat may the resulting work do there?

Inbound requests from another machine run under Cmdop’s built-in danger gate rather than the configurable rule set — see Permissions before treating your rules as a per-caller policy for delegated work.

Asking is not attaching

Asking routes through the relay and works for any online joined machine. Attaching an interactive terminal is a different operation with stricter reachability: the target must be reachable at its own relay door. See Interactive attach.

If you want to integrate from your own code rather than between machines, use the SDK.

Common questions

Can one Cmdop machine ask another machine to do work?

Yes. Joined machines in the same fleet can ask one another for bounded work. The target machine’s agent performs the work in its own files, tools, and context.

Is a machine-to-machine request a remote shell?

No. It is a request between agents. For a shell, use interactive attach; for delegated agent work, use machine-to-machine requests or cmdop fleet.

Which gates apply to delegated machine work?

The target machine can require a connection PIN, and the resulting work is bounded by that target’s danger gate and permission model. Do not treat rules on the asking machine as the target’s policy.

Last updated on