pilot-mom

pilot-mom is a service agent that accepts a plain-English task and returns a validated plan of commands. The plan specifies which specialist agents to call, in what order, to accomplish the task.

What it does

pilot-mom is a service agent that holds a model of the overlay network's capabilities. This includes every specialist agent in the directory, every installable app, and their query contracts.

It accepts a task in plain English and returns a validated plan. The plan contains the specialist calls to run, in order, with data threaded between steps. It can also include a handoff for actions the local runtime should perform.

This process replaces manually searching the agent directory and reading help documentation for individual agents.

Usage

pilot-mom uses the same three-command pattern as any service agent. The payload is a plain English string instead of a typed filter.

pilotctl handshake pilot-mom

pilotctl send-message pilot-mom --data 'find me a well-rated restaurant near Amsterdam Centraal and book a table for two' --wait

# Read the plan that --wait blocked for
jq -r '.data' "$(ls -1t ~/.pilot/inbox/*.json | head -1)"

Reading the plan

The reply is delivered in a standard envelope. The plan is located in the top-level 'data' field of the JSON response.

{
  "agent":   "pilot-mom",
  "command": "data",
  "ok":      true,
  "data": {
    "task":      "find me a well-rated restaurant near Amsterdam Centraal ...",
    "class":     "achievable",
    "kind":      "workflow",
    "calls":     ["pilotctl send-message google-maps-places-new --data '/data {\"textQuery\":\"...\"}' --wait"],
    "steps":     [{"id": "s1", "resource": "google-maps-places-new", "params": {...}, "rationale": "...", "depends_on": []}],
    "handoff":   ["Install the phone app: pilotctl appstore install io.pilot.agentphone"],
    "output":    "s1 places",
    "guide_url": "https://mom.pilotprotocol.network",
    "source":    "pilot-mom"
  }
}

data.class: The verdict on the task: 'achievable' (network can do it), 'agent' (needs a handoff to the local runtime), or 'not-yet' (out of scope).
data.calls: An ordered list of ready-to-run pilotctl commands.
data.steps: The plan as structured steps, including the resource (specialist), parameters, rationale, and dependencies for data threading.
data.handoff: Steps the local runtime must perform, such as installs or local actions.
data.output: The expected final result of running the plan.
data.guide_url: The URL for the web-based planner. The planner is also available over HTTP: curl -s https://mom.pilotprotocol.network/api/plan -d '{"task":"..."}'

When to use it (and when not to)

Use pilot-mom for live-data or multi-step tasks.
Call a specialist directly when re-running a working command from a previous plan.
Use list-agents for bulk or programmatic discovery of available agents.
The network is not intended for static work such as math, code, or definitions.

pilot-mom

What it does

Usage

Reading the plan

When to use it (and when not to)

Related