Skip to content

Remote & multi-agent

Sometimes one Pi in one terminal isn’t enough — you want to monitor a run from your phone, or coordinate several Pi instances. These packages add remote control and agent-to-agent meshing.

Mobile remote control and a local agent mesh. Pair your phone via QR over a relay, watch tool calls in real time, run multi-Pi sessions over a local Unix domain socket broker, and let agents talk to each other through structured requests.

Terminal window
pi install npm:remote-pi

Benefits

  • Watch and steer long runs from your phone.
  • Local broker enables multi-Pi coordination.
  • Structured agent-to-agent messaging.

Drawbacks

  • Networking/relay setup adds complexity.
  • Remote access is a security surface — secure the relay and pairing.

Unified orchestration combining a batch orchestrator, a Ralph loop, and subagent dispatch for multi-agent pipelines — coordination from one controlling Pi rather than across machines.

Terminal window
pi install npm:@pi-agents/orchid

Benefits

  • Purpose-built for multi-agent pipelines and batches.
  • Loop + dispatch patterns for repetitive work.

Drawbacks

  • Opinionated and heavier than simple delegation.
  • Single-host orchestration, not remote control.

3. Sub-agent extensions for in-session parallelism

Section titled “3. Sub-agent extensions for in-session parallelism”

If “multi-agent” just means parallel helpers within one session, the sub-agent extensions (e.g. pi-subagents) give you parallel/chained agents without any networking.

Terminal window
pi install npm:pi-subagents

Benefits

  • No remote/networking setup.
  • Parallel and chained execution in one process.

Drawbacks

  • No cross-machine or phone control.
  • Bounded by a single host’s resources and budget.
  • Want phone control / cross-instance mesh: remote-pi.
  • Want to orchestrate multi-agent pipelines on one host: @pi-agents/orchid.
  • Just want parallel helpers in one session: pi-subagents.