feat: support antigravity target in installer#245
Open
meifans wants to merge 1 commit into
Open
Conversation
14cb9de to
89f166d
Compare
89f166d to
5543e49
Compare
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
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.
This PR adds support for antigravity IDE 2.0 / antigravity cli (referred to as
antigravity) as an installation target.Note
This target configuration is supported starting from Antigravity version 5.20 (released around May 20th). It specifically targets Antigravity 2.0, Antigravity IDE, and Antigravity Cli. Older legacy versions of Antigravity do not support this configuration format. For more details, see Antigravity Downloads.
Why this is needed
Modern versions of
antigravityconfigure their MCP servers globally via~/.gemini/config/mcp_config.jsonand agent instructions via~/.gemini/config/AGENTS.md.MCP Config Specification
Unlike some other targets,
antigravityexpects its MCP server configuration in a specific JSON shape without a"type"property, but retaining an empty"env"block:{ "mcpServers": { "codegraph": { "command": "codegraph", "args": [ "serve", "--mcp" ], "env": {} } } }