What happened
In a Desktop session using Swarm mode, the parent agent scheduled three child agents through Agent Graph and yielded its scheduling turn. While the children continued working, the parent session had no pulsing blue activity indicator in the sidebar, even though the requested task and final summary were still unfinished.
Child sessions are folded under the parent rather than shown as separate top-level entries, so the visible session row makes the task appear idle. The child agents continue executing normally.
Expected: The parent session should continue to indicate ongoing activity while delegated work is running, while the supervisor is waiting to resume, and while the parent generates the final summary. It should return to idle after the task finishes. If user input is required, it should show the appropriate attention state.
How to reproduce
- Run Maka Desktop and create a session in Swarm mode, using a workspace with several packages to review.
- Request parallel work, for example: “Review the storage, runtime-host, and runtime packages. Use one child agent per package, then summarize the findings with concrete evidence.”
- Wait for the parent to schedule the child agents through Agent Graph and call
yield_agent_graph, ending its scheduling turn.
- Observe the parent session's row in the sidebar while the child agents are still running.
- The row has no pulsing blue activity indicator despite the ongoing delegated work.
The exact tool sequence depends on the model. The relevant condition is that the parent has yielded its turn while the graph still has active child work. This was observed with three child agents and reproduced with the actual sidebar components using that state.
Environment
- Maka: Source/development build; process started at
3cfcb09fd.
- The same sidebar behavior was reproduced at source commit
6ce9c72c3, before applying the fix.
- OS: macOS.
- Surface: Desktop session sidebar, backed by Runtime Host.
- Orchestration mode: Swarm.
Logs, screenshots, or additional context
At yield, the tool result reported:
{
"kind": "agent_graph_yielded",
"liveOperatorCount": 3,
"pendingWorkCount": 3
}Timeline reconstructed from persisted events on September 13, 2026 (UTC):
| Time |
Event |
| 07:53:59.172 |
Parent scheduling turn completed with stopReason: graph_yield. |
| 08:08:16.902 |
Last of the three child agents completed. |
| 08:08:17.134 |
Host started a new parent turn for the supervisor wake. |
| 08:09:13.244 |
Parent committed Graph finish with the selected child results. |
| 08:10:37.432 |
Parent finished its final summary. |
The parent had no running turn of its own for approximately 14 minutes and 18 seconds, while the overall task remained unfinished. The wake started approximately 232 ms after the last child completed, so this trace does not indicate a stalled supervisor wake.
On the affected builds, the sidebar derives its activity indicator from the parent session's own running turns and renderer streaming state. Yield correctly completes that turn, but the session catalog and sidebar do not account for the graph's background activity. Streaming child sessions do not make the parent row pulse.
An isolated reproduction using the actual SessionHistoryList and session rail confirmed the missing parent indicator after yield, including when all three children were marked as streaming. The persisted timeline and component reproduction establish the state mismatch; the exact duration of the missing indicator on the original screen was not captured.
A fix should preserve the completed parent turn and its accurate runningTurnIds, while exposing the task's background activity to the session list. Activity should also remain visible after Graph finish if the parent is still generating its summary; an open graph alone should not be treated as evidence of running work.
What happened
In a Desktop session using Swarm mode, the parent agent scheduled three child agents through Agent Graph and yielded its scheduling turn. While the children continued working, the parent session had no pulsing blue activity indicator in the sidebar, even though the requested task and final summary were still unfinished.
Child sessions are folded under the parent rather than shown as separate top-level entries, so the visible session row makes the task appear idle. The child agents continue executing normally.
Expected: The parent session should continue to indicate ongoing activity while delegated work is running, while the supervisor is waiting to resume, and while the parent generates the final summary. It should return to idle after the task finishes. If user input is required, it should show the appropriate attention state.
How to reproduce
yield_agent_graph, ending its scheduling turn.The exact tool sequence depends on the model. The relevant condition is that the parent has yielded its turn while the graph still has active child work. This was observed with three child agents and reproduced with the actual sidebar components using that state.
Environment
3cfcb09fd.6ce9c72c3, before applying the fix.Logs, screenshots, or additional context
At yield, the tool result reported:
{ "kind": "agent_graph_yielded", "liveOperatorCount": 3, "pendingWorkCount": 3 }Timeline reconstructed from persisted events on September 13, 2026 (UTC):
stopReason: graph_yield.The parent had no running turn of its own for approximately 14 minutes and 18 seconds, while the overall task remained unfinished. The wake started approximately 232 ms after the last child completed, so this trace does not indicate a stalled supervisor wake.
On the affected builds, the sidebar derives its activity indicator from the parent session's own running turns and renderer streaming state. Yield correctly completes that turn, but the session catalog and sidebar do not account for the graph's background activity. Streaming child sessions do not make the parent row pulse.
An isolated reproduction using the actual
SessionHistoryListand session rail confirmed the missing parent indicator after yield, including when all three children were marked as streaming. The persisted timeline and component reproduction establish the state mismatch; the exact duration of the missing indicator on the original screen was not captured.A fix should preserve the completed parent turn and its accurate
runningTurnIds, while exposing the task's background activity to the session list. Activity should also remain visible after Graph finish if the parent is still generating its summary; an open graph alone should not be treated as evidence of running work.