Repository navigation
[FEATURE]: Agent event schema and broker adapter #618
Description
Activity
- added a parent issue
on Aug 31, 2026 - added a commit that references this issue
on Sep 1, 2026 - added 13 commits that reference this issue
on Sep 3, 2026 Landed in #619, merged to
nightlyon 2026-09-17 as 6ea85b4.aura_events::agentdefines the event vocabulary andaura::agent_eventsrepublishes it onto the request-scoped brokers, so consumers are unaffected. Parity is covered bycrates/aura-web-server/tests/agent_event_differential.rs, which drives both paths through the real broker registry and asserts byte-identical SSE.Two goals landed with caveats worth recording:
- SSE/A2A/CLI output unchanged — two frames changed shape deliberately:
aura.tool_usagecarries the emitting agent'sAgentContext, andaura.progressbuilds its fallback message fromProgress'sDisplay.AgentContext::agent_iddeserializes with a default so payloads predating the field still parse. - Adoption reversible behind a flag —
ENV_AGENT_EVENTS/agent_events_enabled()readingAURA_AGENT_EVENTSshipped in 6ea85b4 and was removed in f3bdbd6 ([FEATURE]: Single-agent producers emit the agent event schema #620), where the single-agent producers moved ontoagent_events::emitunconditionally. There is no longer a runtime seam to fall back to the broker-only path.
Closing manually: the commits use
Ref:footers, which link but do not close.- SSE/A2A/CLI output unchanged — two frames changed shape deliberately:
- added a commit that references this issue
on Oct 5, 2026
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