Add basic conversation management controls to browser extension#2450
Open
GeorgeNgMsft wants to merge 1 commit into
Open
Add basic conversation management controls to browser extension#2450GeorgeNgMsft wants to merge 1 commit into
GeorgeNgMsft wants to merge 1 commit into
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.
Browser extension:
@conversationmanagement parityBring the browser extension's chat panel to feature parity with the
Shell and CLI for conversation management.
What's new
@conversationslash commands and natural-language phrases work inthe browser chat panel:
new,list,info,switch,prev,next,rename,delete.conversation's history.
conversation) are now visible in the browser panel.
How
A new
chatPanelManageConversationRPC bridges the dispatcher'smanage-conversationaction from the chat panel to the serviceworker, which implements the eight subcommands against the existing
agent-server APIs. Switching follows the bind-new → leave-old →
delete-old ordering used by the CLI to keep the user functional on
errors. A replay gate queues live display events during history reload
so they render in order.