aicentosAntigravity
Google Antigravity does not currently support a custom Base URL — the limitation and available alternatives
Last updated:
Antigravity is Google's agentic IDE. One caveat up front: the official Antigravity desktop IDE does not support custom API endpoints and offers no BYOK (bring your own key). The model picker shows a fixed list maintained by Google and currently cannot point at aicentos.
This document explains the basis for this limitation, how to verify it, and three workable alternative paths.
Why it cannot connect directly
Google's account plans documentation states explicitly that Antigravity does not yet support bring-your-own-model or bring-your-own-endpoint. Several configuration keys circulating in the community (for example antigravity.ai.provider or antigravity.openai-compatible.endpoint written into ~/.antigravity/settings.json) are not officially supported: in practice requests are not routed to the custom endpoint, or silently fall back to the default model, and no custom entry appears in the model picker.
In other words, this is not a case of "the configuration was written wrong" — the current version simply does not expose the capability. The IDE's Settings → Models has no Base URL field to fill in either.
Configuration to fill in
| Field | Value |
|---|---|
| API Key | The key created in the console |
| Base URL | https://aicentos.com/v1 |
| Model | A model name from the Model Gallery in the console |
The table above lists the generic aicentos-side parameters, for use with any of the alternatives below.
Alternatives
Option 1: Switch to Antigravity CLI (recommended, Gemini protocol only)
The command-line tool of the same name, agy, supports endpoint overrides: connecting via GOOGLE_GEMINI_BASE_URL + GEMINI_API_KEY works, but it only accepts the Gemini protocol and can only call Gemini-family models. See Connect Antigravity CLI for the details.
If what you want is "Antigravity's interaction style in the terminal", this is the easiest path.
Option 2: Wrap local models or third-party services as MCP tools
Antigravity's Customizations panel supports registering MCP Servers. You can wrap a local service as an MCP tool and attach it as an invocable tool. Keep in mind: this does not replace the IDE's reasoning model — it just gives the agent one more tool.
Option 3: Community forks or local proxies
- The community fork
open-antigravitysupports any OpenAI-compatible endpoint with custom models — the cleanest path outside the official build. - Some people also use local interception proxies to rewrite the IDE's outbound traffic. This route has no official support, the configuration is fragile and breaks on every upgrade; it is not recommended for production use.
Test
Whichever path you choose, confirm connectivity with a simple prompt first before putting it to real use. For agent-style tasks, start with a small repository.
Notes
- Do not treat "a configuration key appears to exist" as "the feature works". Most
antigravity.*keys inside the IDE are community guesses; writing them produces no error but has no effect either. - If you need the OpenAI-compatible protocol or want to call Claude / GPT-family models, the Antigravity desktop IDE currently cannot do it — prefer clients that support a custom Base URL such as Cursor and Windsurf.
- Antigravity CLI and the desktop IDE are two separate configurations; the CLI's endpoint override does not affect the IDE.
- Before using any third-party fork or proxy, evaluate its security and maintenance status yourself.