Repository navigation
[FEATURE]: Single-agent producers emit the agent event schema #620
Description
Activity
- added a parent issue
on Aug 31, 2026 - added a commit that references this issue
on Sep 1, 2026 Landed in #621, merged to
nightlyas f3bdbd6.All four single-agent emission sites — the hook's
tool_requestedandtool_usage, MCPtool_start, and MCP progress — buildAgentEvents and publish throughagent_events::emit, which routes each payload to the broker it belongs to. An MCP client now holds the request it serves and the agent it serves it for as oneCallContext, so a producer reads both under a single lock and attributes an event only to the request that named it.Differential coverage extends
agent_event_differential.rsto drive the same sequence through the broker calls and throughemit, asserting the SSE frames match.Note for #626/#627: this commit also removed the
AURA_AGENT_EVENTSflag added in #618, so the two paths are no longer selectable at runtime.Closing manually: the commits use
Ref:footers, which link but do not close.- added a commit that references this issue
on Oct 5, 2026
Summary
The single-agent emission sites each call a broker directly, so an agent's output has no shared vocabulary and no single place it passes through. Move them onto the agent event schema, publishing through one entry point that translates to the brokers, so consumers stay unchanged and later work has a seam to attach to.
Goals
Searched Issues
Code of Conduct