Repository navigation
fix: keep Deep Research follow-ups on the current question - #617
Merged
sng-asyncfunc merged 1 commit intoOct 28, 2026
Merged
sng-asyncfunc merged 1 commit into
sng-asyncfunc merged 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.
What changed
Deep Research continuations currently scan conversation history from the beginning, so a follow-up question can be replaced with the topic of an earlier completed turn. Resolve the client's exact
Continue the researchprompt to the most recent user research question instead. Match that prompt exactly so an ordinary question containing “continue” and “research” is not treated as an automatic continuation.Adds synthetic unit coverage for a follow-up after a completed turn, exact continuation-prompt recognition, empty-topic behavior, and trimming the selected latest question. This addresses the behavior described in #589; the relevant earliest-message scan was still present in the inspected
mainsource.Validation
py -3.13 -m pytest tests/backend/services/test_deep_research.py -q— 4 passed.py -3.13 -m py_compile api/services/deep_research.py api/services/research.py tests/backend/services/test_deep_research.py— passed.git diff --check— passed.All validation uses synthetic messages only. No model/provider, embedding, external repository/document, or live service was used.