feat(providers): add Antigravity with V2 and native setup - #308
Merged
Conversation
github-actions
Bot
added
size:XXL
vouch:trusted
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.
Antigravity was missing from the fork's runnable providers and native account setup. This manually ports the official runtime setup, Google authentication, account models, native questions/permissions, workspace commands/skills and text generation onto orchestration V2, with web and Swift account screens.
The port follows upstream
06336460c9988f29c71e839c4c9c840c4552e077and its Antigravity follow-ups through the pinned comparison headd29c56a5c404cb0f58d3b2ac41762fa0d0ac28d4. Installation pins the reviewed 1.1.1 release, verifies the archive before activation and preserves the previous installation on failure. Accounts own isolated profiles and live setup flows. Explicit sign-out, including/logout, closes that account's V2 sessions.V1 adaptations: use the fork's ACP process supervision, interruption quarantine and response receipts; retain subagent batches as V2 tool rows without inventing child IDs or models; route late background commands to their original run. No V1 adapter/task bridge, pagination or SQLite migration is imported. Expo receives only exact question-option and custom-answer compatibility. PATCH.md records these decisions.
Validation: full server run: 4,263 passed, 13 skipped and the two known PortScanner failures. After the final background-routing fix, 328 focused ACP/V2 tests passed. Server/web typechecks, Expo's configured
tsccheck, lint and Swift contract/catalog fixture checks passed. Native app and tests compile; three native setup tests ran on the host. No simulator/browser launch, real Google sign-in, credential import or provider installation was performed; UI screenshots are therefore not available.Implemented with GPT-6 in the Codex harness.