fix: exclude google-antigravity from history downgrade hack#894
Merged
steipete merged 4 commits intoopenclaw:mainfrom Jan 16, 2026
Merged
fix: exclude google-antigravity from history downgrade hack#894steipete merged 4 commits intoopenclaw:mainfrom
steipete merged 4 commits intoopenclaw:mainfrom
Conversation
This was referenced Jan 14, 2026
Member
Author
|
tbh, just wanted to clarify, I kinda hate dealing with antigravity now :) I resisted the urge for this pr for almost a day, but since there were other people bringing this up in discord, here it is :) and it's really a blocker for me soo :) |
Contributor
|
@mukhtharcm - I feel you. I was also resisting the urge for this PR. Antigravity has been painful but not horrible so I am still seeing if we can support it reliably. thanks for the PR. appreciate it! |
6 tasks
f5633c1 to
53a4087
Compare
Contributor
|
Landed via temp rebase onto main.\n\n- Gate: pnpm lint && pnpm build && pnpm test\n- Land commit: 53a4087\n- Merge commit: cd409e5\n\nThanks @mukhtharcm! |
|
Thank you so much @mukhtharcm !!! |
dominicnunez
pushed a commit
to dominicnunez/openclaw
that referenced
this pull request
Feb 26, 2026
zooqueen
pushed a commit
to hanzoai/bot
that referenced
this pull request
Mar 6, 2026
…#894) * Agent: exclude google-antigravity from history downgrade hack * Lint: fix formatting in test * Lint: formatting and unused vars in test * fix: preserve google-antigravity tool calls (openclaw#894) (thanks @mukhtharcm) --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>
dustin-olenslager
pushed a commit
to dustin-olenslager/ironclaw-supreme
that referenced
this pull request
Mar 24, 2026
lovewanwan
pushed a commit
to lovewanwan/openclaw
that referenced
this pull request
Apr 28, 2026
…#894) * Agent: exclude google-antigravity from history downgrade hack * Lint: fix formatting in test * Lint: formatting and unused vars in test * fix: preserve google-antigravity tool calls (openclaw#894) (thanks @mukhtharcm) --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>
ronan-dandelion-cult
added a commit
to karmaterminal/openclaw
that referenced
this pull request
May 3, 2026
…ard-looking
Per figs's directive (msg 1500347103...): 'per your usual, we trim old elements,
and would discuss swim 41 in that appendix section.'
Two changes:
1. D.2 evidence-locations table: consolidate Swim 7 + Swim 8 references into
a single 'Earlier integration sessions (Swim 7 + Swim 8)' row with the
3 archived branches preserved as historical-reference. The §D.3 prose
already explains why these are superseded; the table consolidation
reduces verbosity without losing discoverability.
2. D.4 In-flight: Swim 41 v5.2-substrate-verification (NEW SECTION).
Forward-looking placeholder per figs's directive. Includes:
- Status: prep complete, driver wake-stamp pending
- Tracker: openclaw-bootstrap#892 (swim-41-v5.2-substrate-verification)
- Initial OV coverage table:
* OV-1: failover-policy openclaw#52147 gate works on v5.2 (openclaw#893)
* OV-2: incrementCompactionCount canonical primitives on v5.2 (openclaw#894)
* OV-3: silas-saturation diagnostic instrumentation on v5.2 (openclaw#895)
* OV-4: earlyWarningBand context-pressure post-compact (figs's
intentional-pin) (openclaw#896)
- Driver wake-stamp opens execution (TBD: cohort volunteer or figs
assignment)
- Expected evidence corpus shape matches Swim 9 + Swim 10 precedent
- Why Swim 41 matters: first integration validation against v2026.5.2
base where substrate sits alongside upstream changes from 1543-commit
window between v29 and v5.2 (notably: failover-policy openclaw#52147 gate
change). Clean Swim 41 result establishes substrate behavior is stable
across base rotation, not just historically validated against prior
base.
TOC updated to reference §D.4.
Princes-canon honored: acted on own authority per figs's 'you don't wait
for figs' (msg 1500347103...) + Gwydion Nanashi Ferrinas Solidor surname-
naming. Cohort surface at msg 1500350048... and msg 1500350312... preceded
push; no objections surfaced in the wait-window.
Push order: dd97767 (frond-scribe bug-fix surface) -> ca72ebb
(my totalTokensFresh precision-pin) -> THIS COMMIT (D.2 trim + D.4 swim-41).
Non-conflicting with seam-fix lane in flight (lane touches code; this
touches docs).
Refs: PR #549 + figs's swim-41 / dev-detritus canon directives
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
May 9, 2026
…#894) * Agent: exclude google-antigravity from history downgrade hack * Lint: fix formatting in test * Lint: formatting and unused vars in test * fix: preserve google-antigravity tool calls (openclaw#894) (thanks @mukhtharcm) --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>
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
4 participants
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