Google Antigravity

Antigravity Enterprise Gateway lets Google Antigravity send its model traffic to a gateway your organisation runs, instead of straight to Google. Point it at the AI Gateway, switch it to the OpenAI wire protocol, and every prompt, agent step and tool call from every workstation flows through one governed gateway. Configuration ships as a single admin_settings.json file pushed by your MDM. Developers install Antigravity, open it, and start working. No Google sign-in, no keys to paste. When you’re done:

Antigravity connects to the AI Gateway with no interactive Google sign-in
Developers pick only from the models you approve
Budgets, rate limits and guardrails apply to every request
Every request is logged and attributed to a team, cost center or developer
Fallbacks keep developers working when a provider has an outage

How it works

In gateway mode, Antigravity stops talking to Google. It sends every inference request to the URL in gateway.url, authenticates with the key in gateway.apiKey, and adds any headers you list in gateway.customHeaders. With "wireProtocol": "openai", those requests are standard OpenAI Chat Completions calls, which the AI Gateway serves natively:

Antigravity sends	AI Gateway
`POST {gateway.url}/v1/chat/completions`	The AI Gateway’s universal API endpoint
`Authorization: Bearer <key>`	Accepted as the AI Gateway API key
`gateway.customHeaders` on every request	Read as AI Gateway headers, such as `x-portkey-config` and `x-portkey-metadata`
Streaming responses over SSE	Streamed back chunk by chunk

The AI Gateway then calls the provider with the credentials stored in Model Catalog. No Google Cloud credentials ever reach a workstation.

Supported clients

Client	Minimum version	Through the AI Gateway
Antigravity app	2.15.0	macOS, Windows, Linux
Antigravity CLI (`agy`)	1.2.15	macOS, Linux
VS Code and Visual Studio extensions	CLI 1.2.15, downloaded by the extension
JetBrains IDEs and Zed	1.3.0
Antigravity on the web

JetBrains IDEs and Zed run Antigravity through its ACP server, which supports only the Gemini (genai) wire protocol. The AI Gateway doesn’t serve genai, and when admin_settings.json sets "wireProtocol": "openai", those sessions fail with gateway.wireProtocol 'openai' is not supported by the ACP server. Antigravity on the web has no gateway mode and always requires Google sign-in.

Prerequisites

Requirement	Notes
AI Gateway workspace	Admin access to create providers, configs and API keys
A model provider	Vertex AI for Gemini models. Any provider for other models
An MDM system	Jamf, Microsoft Intune, Ansible, Google Workspace MDM or similar
Supported Antigravity clients	See Supported clients

1. Add a provider

Connect the account the AI Gateway will call on behalf of your developers. For Gemini models, that’s Vertex AI with a service account that has the roles/aiplatform.user role. Go to Model Catalog → Add Provider.

Vertex AI

Gemini through Google Cloud

Gemini API

Google AI Studio keys

AWS Bedrock

Claude and more on AWS

This guide uses a Vertex AI provider with the slug @vertex-prod.

2. Create a config

The config decides where Antigravity’s requests go. Developers never see it, and you can change it without touching a single workstation. Go to Configs → Create Config:

{
  "provider": "@vertex-prod"
}

With the provider pinned here, Antigravity can use plain Gemini model IDs such as gemini-3.8-flash.

Fail over to a second region or project

Keep developers working through a regional outage or quota exhaustion:

{
  "strategy": { "mode": "fallback", "on_status_codes": [429, 500, 502, 503] },
  "targets": [
    { "provider": "@vertex-prod" },
    { "provider": "@vertex-prod-eu" }
  ]
}

See Fallbacks.

Scan prompts and responses with guardrails

Attach input and output guardrails to block secrets, PII or prompt injection before it reaches the model:

{
  "provider": "@vertex-prod",
  "input_guardrails": ["pg-secrets-xxx"],
  "output_guardrails": ["pg-pii-xxx"]
}

Coding agents resend the full conversation on every turn. Prefer guardrails that block or flag over ones that rewrite content, so the history stays consistent. See Guardrails.

3. Create an API key

Go to API Keys and create a key for Antigravity. Attach the config from step 2, then add the controls you want enforced on every request:

Budget Limits

Cap spend per key

Rate Limits

Cap requests or tokens per minute

Guardrails

Enforce content policy

One shared key is the fastest rollout. One key per developer gives per-person budgets and attribution. See Per-developer keys.

4. Test the route

Before touching a workstation, confirm that the AI Gateway answers the exact request Antigravity will make:

curl -N https://aigw.portkey.ai/v1/chat/completions \
  -H "Authorization: Bearer $AIGW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gemini-3.8-flash",
    "stream": true,
    "messages": [{ "role": "user", "content": "Reply with PONG" }]
  }'

Chunks should arrive one by one, and the request should appear in Logs within seconds. Run the same test with every model you plan to list in step 5.

5. Write `admin_settings.json`

admin_settings.json

{
  "gateway": {
    "enabled": true,
    "url": "https://aigw.portkey.ai",
    "apiKey": "YOUR_API_KEY",
    "wireProtocol": "openai",
    "customHeaders": {
      "x-portkey-metadata": "{\"client\":\"antigravity\",\"team\":\"platform-engineering\"}"
    }
  },
  "models": {
    "defaultModelId": "gemini-3.8-flash",
    "list": [
      { "modelId": "gemini-3.8-flash" },
      { "modelId": "gemini-3.7-flash" },
      { "modelId": "gemini-3.1-pro-preview" }
    ]
  }
}

Field	What to set
`gateway.enabled`	`true`. Antigravity routes all inference to the gateway and skips Google sign-in
`gateway.url`	`https://aigw.portkey.ai`, or your hybrid gateway URL. Leave off `/v1`; Antigravity appends `/v1/chat/completions`
`gateway.apiKey`	The AI Gateway API key from step 3. Omit it to use per-developer keys
`gateway.wireProtocol`	`openai`. Required: the AI Gateway doesn’t serve Antigravity’s default Gemini (`genai`) protocol
`gateway.customHeaders`	AI Gateway headers sent on every request. Metadata here tags every log for filtering, analytics and policy
`models.defaultModelId`	The model selected when Antigravity opens
`models.list`	The only models developers can pick. Each `modelId` must resolve through your config
`caCertPath`	Hybrid gateways with a private CA only. Absolute path to your root CA bundle

Settings in admin_settings.json take precedence over environment variables and the developer’s own ~/.antigravity/settings.json, merged field by field. Anything you set here, including the metadata header, can’t be overridden on the workstation.

Offer models from more than one provider

Drop provider from the config and use Model Catalog slugs as model IDs. Each entry then names its own provider:

"models": {
  "defaultModelId": "@vertex-prod/gemini-3.8-flash",
  "list": [
    { "modelId": "@vertex-prod/gemini-3.8-flash" },
    { "modelId": "@vertex-prod/gemini-3.1-pro-preview" },
    { "modelId": "@bedrock-prod/us.anthropic.claude-sonnet-4-5-20250929-v1:0" }
  ]
}

Antigravity’s agent is built and tuned for Gemini. Pilot other models with a small group before listing them for everyone.

6. Deploy with MDM

Antigravity reads the file from a fixed, admin-owned path on each operating system. Ship it with your MDM as a script or package that runs with administrator privileges, so developers can read the file but not edit it.

macOS
Linux
Windows

Path: /Library/Application Support/Antigravity/admin_settings.json

sudo mkdir -p "/Library/Application Support/Antigravity"
sudo install -m 644 -o root -g wheel admin_settings.json \
  "/Library/Application Support/Antigravity/admin_settings.json"

Path: /etc/antigravity/admin_settings.json

sudo install -D -m 644 -o root -g root admin_settings.json \
  /etc/antigravity/admin_settings.json

Path: %ProgramData%\Antigravity\admin_settings.jsonRun in PowerShell as an administrator:

$dir = Join-Path $env:ProgramData "Antigravity"
# Remove any folder a non-admin created first, so they can't keep ownership.
if (Test-Path $dir) { Remove-Item -Recurse -Force $dir }
New-Item -ItemType Directory -Path $dir | Out-Null
# Administrators own the folder; only admins and SYSTEM can write; users can read.
icacls $dir /setowner "*S-1-5-32-544"
icacls $dir /inheritance:r /grant:r "*S-1-5-32-544:(OI)(CI)F" "*S-1-5-18:(OI)(CI)F" "*S-1-5-32-545:(OI)(CI)RX"
Copy-Item admin_settings.json (Join-Path $dir "admin_settings.json")

Assign the package to the device groups that use Antigravity, then restart Antigravity on those machines so it loads the file.

7. Verify

Antigravity app

The status bar shows Connected: Enterprise Gateway, and Account Settings shows Enterprise Gateway Mode Active.

Antigravity CLI

agy -p "Explain binary search in Go"

The answer streams in the terminal with no Google sign-in prompt.

AI Gateway

Open Logs and filter by client = antigravity. Each request shows the model, tokens, cost, latency and any guardrail verdicts.

Per-developer keys

A shared key in admin_settings.json attributes usage to the team. To see and limit usage per person, give each developer their own key:

Create one AI Gateway API key per developer, each with the Antigravity config attached and its own budget.
Remove gateway.apiKey from admin_settings.json. Keep everything else there.
Set AGY_LLM_GATEWAY_API_KEY on each workstation, per user, through your MDM or secrets tooling.

Because settings merge field by field, Antigravity takes the URL, protocol, headers and models from the admin file and the key from the environment.

Sandboxes and CI

Containers, remote SSH hosts and CI runners don’t have an MDM-managed file. Configure them with environment variables or ~/.antigravity/settings.json using the same gateway block, and set the protocol explicitly:

export AGY_LLM_GATEWAY_API_KEY="YOUR_API_KEY"
export AGY_LLM_GATEWAY_WIRE_PROTOCOL="openai"

Use a dedicated key with its own budget for each pipeline so automated runs never spend from a developer’s allowance. Google’s Connect Antigravity to an Enterprise Gateway guide lists every environment variable.

Security

The AI Gateway API key sits on the workstation in plain text. Treat it as a scoped, revocable credential and limit what it can do:

Scope the key. Attach a config, a budget and a rate limit so a leaked key can only reach approved models and spend a capped amount.
Rotate it. Issue a new key, push an updated admin_settings.json, then revoke the old key.
Pin attribution in the admin file. Headers set through AGY_LLM_GATEWAY_HEADERS or the user settings file can be changed by the developer. Only customHeaders in admin_settings.json is tamper-proof from the workstation.
Keep the network private. With a hybrid gateway, expose it only on your corporate network and set caCertPath if it uses an internal CA.

Troubleshooting

Symptom	Fix
Antigravity asks for Google sign-in	The file isn’t at the OS path, or `gateway.enabled` isn’t `true`. Check the path and restart Antigravity.
Requests fail on `/v1beta/models/...` paths	`wireProtocol` is `genai` or unset. Set it to `openai`.
`401 Unauthorized`	The API key is wrong or revoked. Check `gateway.apiKey` or `AGY_LLM_GATEWAY_API_KEY`.
`404` or model not found	The `modelId` doesn’t resolve. Check the provider in the config, or use a `@provider/model` slug.
`gateway.wireProtocol 'openai' is not supported by the ACP server`	The developer is on JetBrains or Zed. Use the app, CLI or VS Code extension.
`x509: certificate signed by unknown authority`	Hybrid gateway with a private CA. Set `caCertPath` to your root CA bundle.
Streams stall or cut off on a hybrid gateway	Disable response buffering for `text/event-stream` on your load balancer and allow requests to run for at least 60 minutes.
Requests start failing after working earlier	A budget or rate limit on the key was reached. Check the key’s limits in Strata Cloud Manager.

Next steps

Configs

Routing, fallbacks, caching and retries

Guardrails

Inspect every prompt and response

Metadata

Attribute usage to teams and developers

Antigravity Enterprise Gateway

Google’s deployment reference

Integrations

LLM Integrations

Cloud Platforms

Guardrails

Plugins

Vector Databases

Agents

AI Apps

Libraries

Observability Providers

Tracing Providers

MCP Clients

MCP Servers

How it works

Supported clients

Prerequisites

1. Add a provider

Vertex AI

Gemini API

AWS Bedrock

2. Create a config

3. Create an API key

Budget Limits

Rate Limits

Guardrails

4. Test the route

5. Write `admin_settings.json`

Offer models from more than one provider

6. Deploy with MDM

7. Verify

Per-developer keys

Sandboxes and CI

Security

Troubleshooting

Next steps

Configs

Guardrails

Metadata

Antigravity Enterprise Gateway

​How it works

​Supported clients

​Prerequisites

​1. Add a provider

Vertex AI

Gemini API

AWS Bedrock

​2. Create a config

​3. Create an API key

Budget Limits

Rate Limits

Guardrails

​4. Test the route

​5. Write admin_settings.json

​Offer models from more than one provider

​6. Deploy with MDM

​7. Verify

​Per-developer keys

​Sandboxes and CI

​Security

​Troubleshooting

​Next steps

Configs

Guardrails

Metadata

Antigravity Enterprise Gateway

How it works

Supported clients

Prerequisites

1. Add a provider

2. Create a config

3. Create an API key

4. Test the route

5. Write `admin_settings.json`

Offer models from more than one provider

6. Deploy with MDM

7. Verify

Per-developer keys

Sandboxes and CI

Security

Troubleshooting

Next steps