You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: Agent Control Surface Parity - structured multi-agent orchestration #5707
Harden Orca's orchestration surface so coordinators can manage multi-agent work through typed messages, tasks, dispatch state, decision gates, and worker lifecycle data instead of terminal text scraping.
Definition of done
Agents can send, reply, check, inbox, and ask with threaded messages, groups, priorities, types, and payload metadata.
Coordinators can create/list/update tasks, dispatch to terminals, inspect dispatches, run/stop loops, and manage decision gates.
Worker completion authority is unambiguous through structured worker_done, heartbeat, escalation, files-modified, report path, task ID, and dispatch ID fields.
Group messages do not create lifecycle events for unrelated workers.
Dispatch and task state survives CLI/runtime restart well enough for coordinators to resume without scraping terminal output.
Immediate slices
Diff orchestration skill guidance against CLI specs.
Move lifecycle fields that exist only as prose into typed flags or validated payloads where possible.
Add structured task/dispatch state responses suitable for restart recovery.
Keep experimental readiness explicit until setup and failure states are agent-readable.
Activity