Summary
Agents publish straight into four process-global brokers keyed by request id, so observing an agent means being an HTTP request. Give agents an event vocabulary of their own, plus an adapter that republishes it onto those brokers, so producers can move over without any consumer changing.
Goals
- An event type covering what an agent surfaces today: tool lifecycle, MCP progress, reasoning and response content, the usage reports, HITL approvals, MCP status.
- Independent of the wire format's serialization constraints, and free of request-scoped correlation, which belongs to whatever observes the agent rather than to the agent.
- SSE, A2A, and CLI output unchanged while the new schema exists alongside the current path.
- Demonstrable parity — a regression test that fails when translation drops or reshapes a field, exercising the real broker registry rather than stubbed channels.
- Adoption incremental and reversible behind a flag, with no producer obliged to move.
Searched Issues
Code of Conduct
Summary
Agents publish straight into four process-global brokers keyed by request id, so observing an agent means being an HTTP request. Give agents an event vocabulary of their own, plus an adapter that republishes it onto those brokers, so producers can move over without any consumer changing.
Goals
Searched Issues
Code of Conduct