feat(gui): agent overview panel — active agents, status chips, recent subagents (#419) - #448
Merged
Merged
Conversation
… subagents (#419) A side panel over the workspace board that answers "what are my agents doing" without opening each conversation. buildAgentOverview derives one orchestrator row per conversation plus a row per task tool_start, pairing each with its tool_end to resolve running/completed/failed; followup presence resolves needs-input. Rows sort attention-first (needs-input > running > failed > idle), current conversation ahead of the rest, newest first within a tier. This is the client half of #419. The cheap-model session recaps land with the engine-side recap events; the panel already renders the status chips and the per-row detail line the recap will populate. Co-Authored-By: Codegraff <blackfloofie@codegraff.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The client half of #419.
A side panel over the workspace board that answers "what are my agents doing" without opening each conversation.
How it derives rows.
buildAgentOverviewwalks every conversation view and emits one orchestrator row per conversation plus one row pertasktool_start. Each start is paired with its matchingtool_end(byrequestId+name+callId) to resolverunning/completed/failed; a pendingfollowupresolvesneeds-input.Attention-first ordering. Rows sort
needs-input>running>failed>idle, current conversation ahead of the rest, newest first within a tier.recentkeeps the last 6 finished subagents so a completed task does not vanish the instant it lands.What is still to come. The cheap-model session recaps land with the engine-side recap events; this panel already renders the status chips and the per-row detail line the recap will populate, so that side is a data change rather than a UI change.
Tests: 4 pass / 0 fail, 11 assertions (
bun test src/components/agent-overview/).