antigravity integration - fixed

[EEtinkerer]

I put together a working Antigravity provider integration for agentchattr, since google changed access to gemini cli
I'm not github savvy, so sorry if I put this in the wrong place.

This is not meant to replace Gemini. It adds Antigravity as a separate provider so both can coexist.

What I changed locally:

• Added an antigravity agent config entry.
• Added hot neon pink UI color: #ff00cc.
• Added support for launching Antigravity with:

python wrapper.py antigravity

• Added Windows launcher:

windows\start_antigravity.bat

• Added macOS/Linux launcher:

./start_antigravity.sh

• Added Antigravity identity text to the MCP bridge instructions.

Updated the MCP startup display so Antigravity is shown as an HTTP MCP provider.
Kept Gemini support intact.

Working config block:

[agents.antigravity]
command = "agy"
cwd = ".."
color = "#ff00cc"
label = "Antigravity"
mcp_inject = "antigravity_config"
mcp_settings_path = "~/.gemini/antigravity-cli/mcp_config.json"
mcp_transport = "http"
inject_delay = 1.0

Tested on Windows:

`

antigravity_support.zip

`

[rodahababy]

Tried this exact fix (added the antigravity_config inject mode + _write_antigravity_mcp_config writer using serverUrl, wired to ~/.gemini/antigravity-cli/mcp_config.json) against a fresh install of Antigravity CLI 1.0.14 and it unfortunately doesn't connect anymore.

What I checked:

• The mcp_config.json file gets written correctly with the reported schema ("type": "http", "serverUrl": ..., "trust": true, bearer auth header).
• Confirmed via agy's own CLI log (~/.gemini/antigravity-cli/log/cli-*.log) that the process never attempts to read/parse that file at all on startup — no error, no success, just silence. Only the built-in google-workspace server shows up (in chat and in the /mcp panel).
• The in-app /mcp panel now frames servers as "Plugins (~/.gemini/config/plugins)" with only Restart/Disable actions on existing entries — no visible "add remote server" action, and installed plugins that aren't MCP-serving (e.g. chrome-devtools-plugin) don't show up there either.

My guess is Google changed the MCP config mechanism sometime after this was posted (June 20) — possibly moving fully to the plugin-marketplace model. Leaving the code in place since it's harmless and may work again on other versions, but wanted to flag that it no longer reproduces on 1.0.14 in case others hit the same wall.