feat(tui): pre-register specialists on PARALLEL_STARTED event#489
Merged
JeremyDev87 merged 1 commit intomasterfrom Feb 17, 2026
Merged
feat(tui): pre-register specialists on PARALLEL_STARTED event#489JeremyDev87 merged 1 commit intomasterfrom
JeremyDev87 merged 1 commit intomasterfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Closes #475
idlenodes in the dashboard agents Map whenPARALLEL_STARTEDevent is received, so they appear in FlowMap early before individualAGENT_ACTIVATEDevents arriveagents.has(id)check)specialist:${name}convention, consistent withresponse-event-extractor.tsand ensuring proper idle→running state transitionsChanges
use-dashboard-state.tsPARALLEL_STARTEDno-op with pre-registration logic (+15 lines)use-dashboard-state.spec.tseventbus-ui.integration.spec.tsxspecialist:${name}formatDesign Decisions
specialist:${name}to avoid collision with general agent IDs and stay consistent withAGENT_RELATIONSHIPeventsmodeforstagefield (notstate.currentMode)Test Plan