I thought adding another account type to my local AI gateway would be a small job.
Open the browser. Get the OAuth code. Exchange it for tokens. Save the account. Done.
That was the theory.
In practice, wiring Antigravity into CliGate turned into a chain of problems that all looked solved until the next request failed.
This is the kind of integration bug that feels trivial from a distance:
the login window opens
Google sign-in succeeds
the success page closes
and then your app still doesn't actually have a usable account
If you've ever built a local developer tool around browser OAuth, this pattern will probably feel familiar.
The Setup
CliGate is a local gateway for AI coding tools.
It lets tools like Claude Code , Codex CLI , Gemini CLI , and OpenClaw talk to one local control plane on localhost , while CliGate handles account pools, API key routing, protocol translation, dashboard chat, and tool-specific config.
The goal for Antigravity support sounded simple:
add Antigravity accounts to the…