Repository navigation
[FEATURE]: Orchestration emits the agent event schema #623
Description
Activity
- added a parent issue
on Aug 31, 2026 - added 7 commits that reference this issue
on Sep 1, 2026 - added 4 commits that reference this issue
on Sep 18, 2026 Landed in #632, merged to
nightlyas two commits:- f227357
refactor(events): define orchestration SSE frames once— collapses the duplicateOrchestrationStreamEventdeclaration. It had already diverged: the CLI-parsed copy inaura-eventscarriedPhaseStarted/PhaseCompletedvariants that nothing emitted. - 30c5f84
feat(events): orchestration emits the agent event schema—OrchestratorEvent's variants move ontoAgentEventPayload, so orchestrated and single-agent runs share one vocabulary andStreamItemcarries that payload directly.
Emitted frames are unchanged; the projection reads the same field sets under a different type, so SSE and A2A moved together.
Closing manually: the commits use
Ref:footers, which link but do not close.- f227357
- added 2 commits that reference this issue
on Oct 5, 2026
Summary
Orchestration already sends its events through a single stream, in band with response content, but in an event type of its own. Separately, the frames those events become are declared twice — once where the server emits them, once where the CLI parses them — with nothing keeping the two in agreement. Put orchestration on the agent event schema and reduce the frame declaration to one.
Goals
Searched Issues
Code of Conduct