Allow threads to run in the background#812
Open
AbhinRustagi wants to merge 16 commits into
Open
Conversation
…enui into ar-background-runs-on-switch
AbhinRustagi
marked this pull request as ready for review
July 23, 2026 06:21
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.
Issue: Currently if an assistant is streaming a request in a thread, and the user switches the chat, the request is aborted and abandoned - bad UX.
Implemented solve:
ThreadStateisCreatingThreadguard: When you send the first message in a brand-new chat,processMessageruns underDRAFT_KEYand then awaitscreateThreadto get a real thread id. During that brief window, the draft slot is "owned" by that in-flight run. If you hit New Chat again during that window,switchToNewThreadwould clear/reset DRAFT_KEY.