@beloved-lenora/opencode-orchestrator

opencode-orchestrator

Fleet command: spawn worker sessions, steer them, stop runaways, retire the finished. One roster, two front doors: agent tools and a dashboard RPC with the same names, so the operator's agent and the dashboard never disagree.

Installation

OpenCode v2 loads the published package from the plugins array in opencode.json:

{
  "plugins": ["@beloved-lenora/opencode-orchestrator@latest"],
}

Then restart the service (opencode service restart) so the plugin loads.

Tools

Tool	Does
fleet_spawn	Start a worker session on a task. Returns its session id.
fleet_send	Send a follow-up prompt to a roster session (queue by default, steer to interrupt and inject).
fleet_stop	Interrupt a roster session's current run.
fleet_retire	Delete a roster session and drop it from the roster.
fleet_roster	List roster sessions with alive/gone flags.
fleet_adopt	Track an existing session without briefing it.

The dashboard exposes the same operations plus a per-session summary that combines the goal, checklist, guard, and Q&A states. A missing source yields empties, never an error. Every mutation emits a change event the dashboard subscribes to, so it stays current without polling.

Managed vs adopted

Sessions spawned here are managed: every prompt they receive carries standing orders (work the task, report concisely, never approve permissions for anyone). Adopted sessions are monitored only and never rewritten.

The roster holds 20 sessions. Liveness is checked on read, so gone sessions show as gone instead of erroring.

Dashboard

• Sidebar roll-up: session count with this session's position, worker count, permission-attention and busy counts.
• /fleet dashboard: per-session cards sorted by recent activity (title, busy/attention/idle status, context bar, message counts, spend, queue). spawn worker sits in the header. Click a card to drill into transcript stats, the live summary section, and the action row. Roster sessions get send / steer / stop / retire (confirm-gated); strangers get adopt into fleet.

Boundaries, deliberate

• send is roster-only. The fleet cannot steer strangers.
• Default delivery is queue; steer is opt-in per call.
• Permissions are never auto-approved. Pending approvals show as permission requests in the dashboard, answered by the operator.
• retire deletes the session.