fix: queue concurrent subagent questions#36916
Open
lucas-gaitzsch wants to merge 1 commit into
Open
Conversation
Contributor
|
The following comment was made by an LLM, it may be inaccurate: Based on my search, I found one potentially related PR that might be worth reviewing in context: Related PR:
However, this appears to be addressing a different but complementary aspect (preserving session work) rather than a duplicate of the current PR's focus on queueing and routing concurrent subagent questions. The current PR (#36916) is the primary PR implementing the queue management for concurrent subagent questions and does not appear to have exact duplicates in the open PR list. |
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.
Issue for this PR
Closes #36915
Type of change
What does this PR do?
Collects pending questions across the full root session tree, orders them by request ID, and keeps the active request selected until it resolves.
The TUI now remounts prompt state per request, preserves interrupted drafts, blocks duplicate submissions, and routes replies through the owning session location. Desktop/web uses the same sticky queue selection and owner-location routing.
How did you verify your code works?
packages/tui: 194 passed, 1 skipped; typecheck passed.packages/app: targeted queue tests and typecheck passed.Screenshots / recordings
Not applicable; this changes request selection and routing without changing the UI.
Checklist