fix: track new Gemini interaction id on follow-up - #131
Draft
cursor[bot] wants to merge 1 commit into
Draft
Conversation
Gemini's Interactions API mints a new interaction id for each follow-up. Discarding that id left status/output polling stuck on the completed prior turn. Propagate and re-key the session id in CLI state and the web store. Co-authored-by: Parvez Kose <koseparvez@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Bug and impact
Gemini follow-ups create a new Interactions API id (
previous_interaction_idchains history). We discarded that id and kept polling/storing the old completed interaction, so follow-ups appeared to snap back to completed and their progress/output were untrackable.Root cause
realGeminiPort.sendFollowupignored the POST/interactionsresponse id. CLI + web follow-up paths never re-keyed persisted session state.Fix
StateStoreand Supabase session rows when the vendor mints a new idsessionIdfrom the follow-up API and point the drawer at the new idValidation
npm test(root + web): all passing, including new rekey / Gemini follow-up coverage