You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
impact: MCU voice turns return to idle after the parent response and later speak only the final autonomous Agent response produced for completed background work.
6
+
---
7
+
8
+
The Global Agent server and the direct outbound MCU relay compatibility path
9
+
keep a hidden session listener while a voice-triggered Hermes run has pending
10
+
background delegations. Subagent telemetry and delegation lifecycle events
11
+
remain server-internal and are not forwarded to the MCU. When the background
12
+
completion starts its autonomous parent turn, the listener buffers that turn
13
+
and reuses the existing MCU audio queue only after `run.completed` provides the
14
+
final Agent output. Existing MCU firmware and the transparent remote relay
15
+
server require no protocol changes. An MCU interrupt received after the parent
16
+
turn is already idle no longer records a deferred session abort, so immediately
17
+
starting another recording leaves pending background delegations running; an
18
+
interrupt during an active foreground turn still aborts that turn normally.
19
+
Each MCU foreground run now carries an internal `queue_id`. When a new voice
20
+
turn is queued while an autonomous background delivery is returning on the
21
+
same chat session, MCU listeners use that identifier to keep the two event
22
+
streams separate. The existing background listener owns the autonomous result;
23
+
the new listener ignores it until its own queued run starts. This identifier is
24
+
not part of the MCU wire protocol, so older firmware remains compatible.
0 commit comments