feat: add /btw side-question threads#142
Merged
GCWing merged 2 commits intoGCWing:mainfrom Mar 13, 2026
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
2 participants
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.
This PR introduces /btw side-question threads. From the main session, users
can run /btw ... to create a child session (side thread), and a lightweight
in-stream marker card is inserted into the parent chat so you can jump to the
thread quickly. The Sessions list is updated to better represent parent/child
relationships, and related i18n strings are added.
On Desktop, it adds BTW Tauri commands btw_ask, btw_ask_stream, and btw_cance
l, with streaming delivered via btw://text-chunk, btw://completed, and
btw://error events. It also includes a UX fix to make marker focusing stable
after scrolling in the virtualized message list (wait for Virtuoso to settle
and use auto scroll behavior to avoid recycled DOM issues).