Feature: coordinator collateral panel and scoped per-node live output#7
Merged
Merged
Conversation
Signed-off-by: Ibrahim Kazimov <74775400+ibrahimkzmv@users.noreply.github.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
1 participant
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.
What
Adds a collapsible COORDINATOR panel in the right collateral column for planning traces and streams, while keeping the DAG limited to real task-to-task routing. LIVE_AGENT_OUTPUT in node details is scoped to the selected agent/task. Plan events emit a coordinator trace line; shared helpers filter coordinator vs worker traces.
Why
Coordinator output was mixed into every node’s live output and was briefly modeled as a DAG node, which misrepresented the graph. Planning is global orchestration, not a task dependency so it belongs in collateral UI, not on the canvas.
Screenshots
Checklist
npm run lintpassesnpm testpasses