fix: exclude google-antigravity from history downgrade hack #894
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 PR excludes the
google-antigravityprovider from thedowngradeGeminiHistorymechanism insanitizeSessionHistory.The
downgradeGeminiHistoryfunction converts structured tool calls into simple text, which was a workaround for other Google/Gemini models. However,google-antigravityhandles tool calls natively, and this conversion was "poisoning" the history, causing tool calls to be treated as plain text and not executed.Fix Details
sanitizeSessionHistoryinsrc/agents/pi-embedded-runner/google.tsto accept aproviderargument.downgradeGeminiHistoryif the provider isgoogle-antigravity.compact.tsandattempt.tsto pass the provider.src/agents/pi-embedded-runner.sanitize-session-history.test.tsto verify the exclusion.Fixes #893