feat: add busy input mode selector (queue/interrupt/steer) to main chat - #2454
Open
tcszh wants to merge 2 commits into
Open
feat: add busy input mode selector (queue/interrupt/steer) to main chat#2454tcszh wants to merge 2 commits into
tcszh wants to merge 2 commits into
Conversation
The WebUI input box was never locked, but messages sent while the AI was working were silently queued until the current run finished — with no way to interrupt or steer. This adds a real, working control for the existing busy_input_mode setting: - DisplaySettings: NSelect dropdown with Queue / Interrupt / Steer - chat store sendMessage: steer mode rewrites the message to /steer while a bridge run is live (skipped for coding-agent sessions and explicit slash commands); interrupt mode emits abort and waits for abort.completed before sending, so the new message is processed immediately - i18n: en/zh labels and hints for the three modes - tests: flip the old 'does not expose the unwired toggle' assertion to positive coverage (selector visible, mode saved)
Harness requires a docs/chat-chain-changes fragment when the chat session chain is touched (chat.ts changed for the busy input mode feature).
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.
What
The WebUI input box was never locked, but messages sent while the AI is processing were silently queued until the current run finishes — with no way to interrupt or steer. This makes the existing (previously unwired)
busy_input_modesetting actually work in the main chat, giving users the same interrupt/steer semantics the CLI has.Changes
sendMessage:steermode: while a bridge run is live, rewrite the message to/steer <text>so it is injected into the current run instead of queued (skipped for coding-agent sessions and explicit slash commands)interruptmode: emitabortand wait forabort.completedbefore sending, so the new message is processed immediatelyWhy
Investigation showed the WebUI only had a queue — no interrupt/steer entry point for the main chat (group chat already had
interruptAgent).busy_input_modeexisted only in API types and i18n strings; this wires it up end-to-end, client-side only (server already handlesabortand/steer).Verification
vue-tsc -bpassesdisplay-settings.test.ts7/7 pass (new positive tests)npm run buildpasses; built artifacts containbusy_input_mode||"queue",abort.completed, and the three option labels