Antigravity models not working

[KevinGastelum]

Requested entity was not found.
[Debug Info]
Requested Model: gemini-3-pro-preview
Effective Model: gemini-3-pro-preview
Project: positive-light-z4p9v
Endpoint: https://cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse
Status: 404
Request ID: N/A
Tool Debug Missing: 0
Tool Debug Summary: idx=0, hasCustom=true, customSchema=true, hasFunction=false, functionSchema=false
Tool Debug Payload: [{"functionDeclarations":[{"name":"bash","description":"Executes a given bash command in a persistent shell session with optional timeout, ensuring proper handling and security measures.\n\nAll commands run in C:\Users\x\x\x\x by default. Use the workdir parameter if you need to run a command in a different directory.\n\nBefore executing the command, please follow these steps:\n\n1. Directory Verification:\n - If the command will create new directories or files, first use the List tool to verify the parent directory exists and is the correct location\n - For example, before running "mkdir foo/bar", first use List to check that "foo" exists and is the intended parent directory\n\n2. Command Execution:\n - Always quote file paths that contain spaces with double quotes (e.g., rm "path with spaces/file.txt")\n - Examples of proper quoting:\n - mkdir "/Users/name/My Documents" (correct)\n - mkdir /Users/name/My Documents (incorrect - will fail)\n - python "/path/with spaces/script.py" (correct)\n - python /path/with spaces/script.py (incorrect - will fail)\n - After ensuring proper quoting, execute the command.\n - Capture the output of the command.\n\nUsage notes:\n - The command argument is required.\n - You can specify an optional timeout in milliseconds (up to 600000ms / 10 minutes).\n If not specified, commands will timeout after 120000ms (2 minutes).\n - The description argument is required. You must write a clear, concise

oh-my-opencode.json:
{
"google_auth": false,
"agents": {
"frontend-ui-ux-engineer": { "model": "google/gemini-3-pro-high" },
"document-writer": { "model": "google/gemini-3-flash" },
"multimodal-looker": { "model": "google/gemini-2.5-flash" },
"Sisyphus": { "model": "opencode/big-pickle" },
"librarian": { "model": "opencode/big-pickle" },
"oracle": { "model": "opencode/big-pickle" }
}
}

[fparrav]

Solution Found ✅

The issue is caused by missing google_auth: false in the oh-my-opencode.json configuration file.

Fix

Add this to your ~/.config/opencode/oh-my-opencode.json (or .opencode/oh-my-opencode.json):

{
  "google_auth": false,
  "agents": {
    "frontend-ui-ux-engineer": { "model": "google/gemini-3-pro-high" },
    "document-writer": { "model": "google/gemini-3-flash" },
    "multimodal-looker": { "model": "google/gemini-2.5-flash" }
  }
}

Why This Works

According to the README documentation:

When using opencode-antigravity-auth, disable the built-in auth and override agent models in oh-my-opencode.json

The google_auth: false setting disables the built-in Google auth that conflicts with the opencode-antigravity-auth plugin.

Verification

After adding this configuration, restart OpenCode and the Antigravity models should work without the 404 error.

Tested and confirmed working! 🎉

[KevinGastelum]

I do have "google_auth": false here, its also in my original message:
oh-my-opencode.json:
{
"google_auth": false,
"agents": {
"frontend-ui-ux-engineer": { "model": "google/gemini-3-pro-high" },
"document-writer": { "model": "google/gemini-3-flash" },
"multimodal-looker": { "model": "google/gemini-2.5-flash" },
"Sisyphus": { "model": "opencode/big-pickle" },
"librarian": { "model": "opencode/big-pickle" },
"oracle": { "model": "opencode/big-pickle" }
}
}

[fparrav]

my bad, I skimmed through your original message too fast and completely missed that you already had "google_auth": false in there. Sorry about that.
Since your config looks right but it's still not working, could you share your antigravity-accounts.json file? Just make sure to hide any sensitive stuff like tokens or account details before posting.
Also, when I ran into weird auth issues with this setup, what actually fixed it for me was just deleting antigravity-accounts.json and going through the whole auth flow again from scratch. Sometimes the credentials just get in a weird state. Might be worth a shot if nothing else turns up.