fix(queue): scope error and research detection to active UI (#44) - #63
Merged
MarsLuay merged 1 commit intoSep 20, 2026
Merged
Conversation
Ignore historical conversation phrases when classifying ChatGPT error, retry, and Deep Research state. Match only the current response surface, report the selector that fired, and treat missing status UI as unknown instead of a false error.
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.
Summary
ChatGPT error, retry, and Deep Research detection now reads only the active response surface (current turn or non-historical status/alert/stop/retry UI). Historical conversation text no longer pauses a healthy queue or fakes research. Missing status UI is reported as unknown/compatibility.
Test plan
npm run check(166 tests, ESLint, typecheck)Closes #44