Antigravity counts through the gateway on a Gemini API key. A new gemini gateway route (https://generativelanguage.googleapis.com) takes Antigravity CLI's Gemini API calls: the model comes from the request path (…/models/<model>:generateContent or :streamGenerateContent), usage maps usageMetadata (cached prompt tokens as cache reads, thinking as output; streamed chunks are cumulative, the last wins), org model rules match gemini/<model>, refusals come back in Google's error shape so agy shows them, an API key sent as ?key= never enters a cache key, and compression touches only Gemini text parts and function responses. hnl gateway connect antigravity works when Antigravity runs in Gemini API-key mode ("modelProvider": "gemini" in ~/.gemini/antigravity-cli/settings.json): it exports GOOGLE_GEMINI_BASE_URL for new terminals in a marked block in ~/.zshrc, ~/.bashrc (and an existing ~/.bash_profile on macOS) or ~/.config/fish/conf.d/hnl-gateway.fish, or as a Windows user variable, refuses when the variable already points elsewhere, and disconnect removes exactly that block. Signed in with a Google account, Antigravity's calls still go straight to Google: connect changes nothing and says how to switch, hnl gateway connect with no harness named skips it, and hnl gateway status shows which mode it is in.

Usage's "Models from … aren't in this table" notice listed the old HarnessLink agent as a harness and told you to run hnl gateway connect superpi and hnl gateway connect antigravity, neither of which can work, and its text ran two words together ("sotheir"). The old built-in agent is no longer a harness: usage coverage leaves it out entirely. Antigravity is named with the reason it can't be counted (its signed-in traffic goes straight to Google), and commands are offered only for harnesses the gateway can route (Claude Code, Codex, omp, pi).

Flag notifications