Repository navigation
feat(web): send follow-ups into the active turn - #973
Merged
Merged
Conversation
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.
Description
Follow-ups entered while the agent was working could only wait for the next turn. Add Send now to the web composer and each queued prompt so text reaches the active turn at the next model/tool boundary while running tools continue.
session.steergateway method and a thread-safe inbox for the active query. Persist delivered input and check for follow-ups before the turn finishes.Validation
cd ui-web && npm run check— type checks and 756 tests passed.cd ui-web && npm run build— passed.New Feature Submissions
All Submissions