Skip to content

[Feature]: Agent Control Surface Parity - structured multi-agent orchestration #5707

Closed

Description

@wolfiesch

Parent: #5700
Suggested labels: enhancement, agent-workflow, P1

Summary

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.

Related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

size/lLarge PR (≤2500 added lines, ≤50 files)

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions