🤖 fix: detect and abort repetitive Gemini output to prevent token exhaustion #828
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
This addresses the known Gemini token exhaustion bug where the model gets stuck in a loop emitting variations like
I am done. I am done. I am done...until it exhausts all output tokens.The Bug
This is a well-documented issue with Gemini models:
The gemini-cli implements loop detection to catch this, and now we do too.
The Fix
RepetitionDetectorclass that monitors streaming text for repetitive patterns using a sliding window approachTesting
RepetitionDetectorclass covering:I am done. I am done.)addTextcallsGenerated with
mux