Repository navigation
fix(antigravity): accept supported legacy handshake versions - #12509
juliusmarminge merged 1 commit into
Conversation
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — The PR narrowly fixes Antigravity installation validation for a supported legacy handshake and adds focused coverage for accepted and rejected protocol versions. Existing wire-format selection remains unchanged, keeping the runtime risk limited. You can add or adjust custom eligibility rules. Learn more. |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: unavailable · PR result: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
Antigravity 1.1.1 echoes protocol version 2 while returning legacy ACP fields. V2 requests 2, but the installer required 1, so the correct pinned runtime failed with a generic identity error.
Accept the known versions 1 and 2 while retaining the identity, release, and capability checks. The existing response-shape negotiation continues to select legacy session messages. Other protocol versions remain rejected; there is no global downgrade.
Verification:
Before: the version-2 fixture failed installation. After: it passes while prompt completion still uses the legacy RPC result. No credentials, real provider sessions, or runtime archive downloads were used. Authenticated Antigravity chat remains unverified. This is backend behavior, so screenshots do not apply.
Base:
t3code/codex-turn-mapping. Bottom of the requested two-PR provider diagnostics stack.Model: GPT-6. Harness: Codex.