Conversation
…s, Tab to fill When a turn ends the server reads the tool calls it just stored and offers up to three specific follow-ups: follow the run that was launched, show its output, launch the dry run for real, summarize a run that completed, explain one that failed, open the file a search cited, run the workflow that was inspected, check on delegated agents. No extra model call; the suggestion is grounded in what happened. A reply that asked the user something offers nothing, since the next thing to type is the answer. The first suggestion becomes the composer's placeholder while the box is empty and Tab fills it in, as a terminal completes a command; the others sit as chips above the composer. Typing hides them. The composer belongs to the chat package, so this attaches to its textarea from outside, as the slash palette does. Four tests on the rules.
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.
When a turn ends,
GET /api/chat/suggestions?conversation=<id>reads the tool calls stored with the last assistant turn (suggestNext) and offers up to three specific follow-ups: follow the run that was launched or show its output, launch a dry run for real, summarize a completed run, explain a failed one, open the file a search cited, run the workflow that was inspected, check on delegated agents, retry a failed tool step; a long plain answer gets "sources" and "save as a note". No extra model call. A reply ending in a question orNEEDS DECISION:offers nothing, and so does a conversation where the user spoke last.NextUpattaches to the package's composer textarea from outside (as the slash palette does): the first suggestion becomes the placeholder with "(Tab)" while the box is empty, Tab fills it through the native setter and an input event, the rest are chips above the composer, and typing hides everything. The palette's capture-phase Tab wins when it is open. Four tests on the rules; 151 server and 9 web pass.