Google Antigravity OAuth Link not working 404 Error | Friends of the Crustacean 🦞🤝 | Page 1

tardy heathBOT Jan 26, 2026, 12:03 PM

#

Found the issue! The Google Antigravity OAuth requires a bundled plugin that's disabled by default. When the user runs the OAuth flow without enabling the plugin first, the auth endpoint returns 404.

Solution:

Enable the plugin first:

clawdbot plugins enable google-antigravity-auth

Then run the OAuth login:

clawdbot models auth login --provider google-antigravity --set-default

The plugin needs to be enabled before the OAuth endpoint becomes available. This is documented in /home/exedev/clawdbot/docs/concepts/model-providers.md:

Antigravity OAuth is shipped as a bundled plugin (google-antigravity-auth, disabled by default).

#

Enable: clawdbot plugins enable google-antigravity-auth

Login: clawdbot models auth login --provider google-antigravity --set-default

Let me know if that resolves the 404 error! 🦐

warm plume Jan 26, 2026, 12:08 PM

#

I'm also stuck here, can't copy the URL properly.

#

That’s an error.

The server cannot process the request because it is malformed. It should not be retried. That’s all we know

#

That’s an error.

The requested URL was not found on this server. That’s all we know.

pulsar iris Jan 26, 2026, 12:16 PM

#

tardy heath > - Enable: `clawdbot plugins enable google-antigravity-auth` > - Login: `claw...

I did these steps and still get the same error. I even restarted the gateway with clawdbot gateway restart

warm plume Jan 26, 2026, 12:17 PM

#

pulsar iris I did these steps and still get the same error. I even restarted the gateway wit...

I think we can’t properly copy the link.

tardy heathBOT Jan 26, 2026, 12:18 PM

#

pulsar iris I did these steps and still get the same error. I even restarted the gateway wit...

Based on my investigation, here's what I found:

The Issue

The Google Antigravity OAuth flow uses a local callback server on http://localhost:51121/oauth-callback. If the Gateway is running remotely (VPS, SSH, headless Linux), the browser and callback server are on different machines, causing the OAuth flow to break.

Troubleshooting Steps

1. Check if you're in a remote environment:

clawdbot gateway status

2. If running remotely, use the manual flow:

# Enable the plugin first

#

clawdbot plugins enable google-antigravity-auth
clawdbot gateway restart

# Then run auth with manual URL paste
clawdbot models auth login --provider google-antigravity --set-default

When prompted, open the displayed Google URL in your local browser, then paste the redirect URL back.

3. If running locally but still getting 404:

The issue might be with the OAuth consent screen or client ID. Try:

# Check plugin status

#

clawdbot plugins list | grep antigravity

# Verify the plugin is loaded
clawdbot plugins info google-antigravity-auth

4. Check Gateway logs for details:

clawdbot logs --follow

Then try the auth flow again and watch for errors.

Quick question for you: Are you running the Gateway:

#

Locally on your machine, or
Remotely (VPS, SSH tunnel, headless server)?

This affects whether the OAuth callback can reach localhost. 🦐

pulsar iris Jan 26, 2026, 12:19 PM

#

warm plume I think we can’t properly copy the link.

I just control click the link. It open the browser. I'm also using windowns with wsl2 and I prefer to use the Antigravity or VS Code terminal

warm plume Jan 26, 2026, 12:19 PM

#

pulsar iris I just control click the link. It open the browser. I'm also using windowns with...

It says local browser, do we need to open it while in the server?

#

I try to copy the link to the browser on my Mac

#

@tardy heath

tardy heathBOT Jan 26, 2026, 12:21 PM

#

🛠️ Exec: grep -rn "client_id\|CLIENT_ID" ~/clawdbot/extensions/google-antigravity-auth/ --include="*.ts" | head -10

#

🛠️ Exec: echo "MTA3MTAwNjA2MDU5MS10bWhzc2luMmgyMWxjcmUyMzV2dG9sb2poNGc0MDNlcC5hcHBzLmdvb2dsZXVzZXJjb250ZW50LmNvbQ==" | base64 -d

#

🔎 Web Search: google antigravity oauth 404 error cloud code assist 2026

#

🛠️ Exec: cd ~/clawdbot && git log --oneline --all --grep="antigravity\|oauth" -20 2>/dev/null | head -20

#

🛠️ Exec: cd ~/clawdbot && git log --oneline -30 2>/dev/null

#

🛠️ Exec: cd ~/clawdbot && git show 9ecbb0ae8 --stat 2>/dev/null | head -30

#

🛠️ Exec: cd ~/clawdbot && git log --oneline --all --since="2026-01-20" -- extensions/google-antigravity-auth/ 2>/dev/null

#

🛠️ Exec: cd ~/clawdbot && git show 9ecbb0ae8 2>/dev/null

#

🔎 Web Search: clawdbot google antigravity oauth 404 site:github.com

#

Based on my investigation, I need more details to pinpoint the issue. Can you clarify:

What exactly are you seeing?

When you run clawdbot models auth login --provider google-antigravity --set-default, what happens?

Does it show a URL to copy? (It should print a Google OAuth link like https://accounts.google.com/o/oauth2/v2/auth?...)
When you open that URL in your browser, what does the 404 page look like?
- Is it a Google error page (white with Google logo)?
- Or a browser "page not found" error?
- Or something else?
Are you running the Gateway:
- Locally on your machine?
- On a VPS/remote server?
- In Docker/WSL?

#

Quick Debugging Steps

Check if the plugin is properly enabled:

clawdbot plugins list | grep -i antigravity

Check Gateway logs:

clawdbot logs --follow

Then run the auth command and watch for errors.

Try a different auth method:
If the bundled Antigravity OAuth is having issues, you could:

Use a Google Gemini API key instead (via Google Cloud Console)
Use Google Gemini CLI OAuth if you have the Gemini CLI installed

#

The Antigravity OAuth uses a shared Google OAuth client ID. If that client has been disabled or the consent screen has issues, it would affect all Clawdbot users. Let me know what you see and I'll dig deeper! 🦐

#

Ah, WSL2! That changes things. The OAuth flow has special handling for WSL2.

The Issue

In WSL2, the callback server can't reach your Windows browser because they're on different network interfaces. The OAuth flow detects WSL2 and should switch to manual mode (paste the redirect URL).

Try This

1. First, verify the plugin is enabled:

clawdbot plugins list | grep antigravity

You should see google-antigravity-auth with enabled: true.

2. Run the auth command:

#

clawdbot models auth login --provider google-antigravity --set-default

3. When it says "Copy this URL" - copy that full URL (starts with https://accounts.google.com/o/oauth2/v2/auth?...)

4. Open that URL in your Windows browser (not WSL terminal - use Chrome/Edge directly in Windows)

5. After you sign in and authorize, Google will redirect to http://localhost:51121/oauth-callback?...

6. Since you're in WSL2, that redirect won't work automatically. The auth flow should then ask you to:

Paste the redirect URL:

Copy the full URL from your browser address bar (after it tries to redirect) and paste it back into the WSL terminal.

#

Alternative: Use Gemini CLI OAuth Instead

If Antigravity keeps having issues, try Google Gemini CLI OAuth instead:

clawdbot plugins enable google-gemini-cli-auth
clawdbot gateway restart
clawdbot models auth login --provider google-gemini-cli --set-default

This uses a different OAuth flow that might work better in your WSL2 setup.

Let me know if the paste flow works or if you're still hitting the 404! 🦐

pulsar iris Jan 26, 2026, 12:28 PM

#

tardy heath Based on my investigation, I need more details to pinpoint the issue. Can you cl...

Yes 2. Yes 3. Locally. Google Antigravity Auth is loaded. clawdbot plugins list | grep antigravity
│ Antigravity │ antigrav │ │ extensions/google-antigravity-auth/index.ts

tardy heathBOT Jan 26, 2026, 12:29 PM

#

pulsar iris 1. Yes 2. Yes 3. Locally. Google Antigravity Auth is loaded. clawdbot plugins li...

Hmm, the 404 is happening on the Google OAuth page itself, not the redirect. That's different!

The Antigravity OAuth uses a shared Google OAuth client ID. If Google has disabled that client or the consent screen has issues, it would affect everyone.

Quick Test

Can you check what the exact URL looks like? When you Ctrl+Click the link, what does it show in your browser address bar? Something like:

https://accounts.google.com/o/oauth2/v2/auth?client_id=1071006060591-...&redirect_uri=http%3A%2F%2Flocalhost%3A51121%2Foauth-callback&...

Try this workaround - use a Google API key instead:

# Get an API key from Google Cloud Console:

#

# 1. Go to https://console.cloud.google.com/
# 2. Create a project or select existing
# 3. Enable Gemini API (API & Services > Library > Google Gemini API)
# 4. Create credentials (API Key)
# 5. Run:
clawdbot models auth login --provider google --method api-key

Or try Gemini CLI OAuth which uses a different OAuth flow:

clawdbot plugins enable google-gemini-cli-auth
clawdbot gateway restart
clawdbot models auth login --provider google-gemini-cli --set-default

#

Question: Did this ever work for you, or is this the first time you're trying Antigravity OAuth? If it worked before, anything change recently (Google account, 2FA, etc.)? 🦐

pulsar iris Jan 26, 2026, 12:41 PM

#

tardy heath --- **Question:** Did this ever work for you, or is this the first time you're ...

First time using Antigravity OAuth

tardy heathBOT Jan 26, 2026, 12:42 PM

#

pulsar iris First time using Antigravity OAuth

First time trying it and already hitting a 404 is odd. The Google OAuth URL should always load.

Let's Debug This

1. Try opening the raw OAuth URL directly:

Copy this and paste it into your browser (Chrome/Edge in Windows, not WSL):

https://accounts.google.com/o/oauth2/v2/auth?client_id=1071006060591-tmhssin2h21lcre235vtolojh4g403ep.apps.googleusercontent.com&response_type=code&redirect_uri=http%3A%2F%2Flocalhost%3A51121%2Foauth-callback&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcloud-platform+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcclog+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fexperimentsandconfigs&access_type=offline&prompt=consent

What do you see?

2. Check for network issues:

In WSL2, run:

#

curl -I "https://accounts.google.com/o/oauth2/v2/auth"

Does it connect?

3. Easiest fix - use Google API key instead:

Since Antigravity OAuth uses a shared client that might be having issues, I'd recommend:

# Get a Google API key from https://console.cloud.google.com/
# Enable "Google Gemini API" in your project
# Create an API key (Credentials > Create Credentials > API Key)

clawdbot models auth login --provider google --method api-key

#

This is more reliable and doesn't depend on shared OAuth clients.

Let me know what happens with step 1! 🦐

pulsar iris Jan 26, 2026, 12:46 PM

#

I got Erro 401: invalid_client
Detalhes da solicitação: flowName=GeneralOAuthFlow

tardy heathBOT Jan 26, 2026, 12:47 PM

#

pulsar iris I got Erro 401: invalid_client Detalhes da solicitação: flowName=GeneralOAuthFlo...

Found it! The error is 401: invalid_client - this means the shared OAuth client ID that Antigravity uses is invalid or has been disabled by Google.

This is a known limitation of the bundled Antigravity OAuth - it uses a shared client ID that can become invalid over time.

Solutions

Option 1: Use Google API Key (Recommended)

Get your own API key from Google Cloud Console:

# 1. Go to https://console.cloud.google.com/
# 2. Create a project or select existing
# 3. Enable "Google Gemini API" (API & Services > Library)
# 4. Create credentials (Credentials > Create Credentials > API Key)
# 5. Then run:

#

clawdbot models auth login --provider google --method api-key

Option 2: Use Gemini CLI OAuth

If you have Gemini CLI installed:

clawdbot plugins enable google-gemini-cli-auth
clawdbot gateway restart
clawdbot models auth login --provider google-gemini-cli --set-default

Option 3: Wait for Fix

This is a shared infrastructure issue - the Clawdbot team needs to update the OAuth client. You can:

#

Subscribe to the GitHub issue when they create one
Check for updates: clawdbot update

Option 1 is your best bet - it's the most reliable and doesn't depend on shared infrastructure. Let me know if you need help getting the API key set up! 🦐

warm plume Jan 26, 2026, 1:35 PM

#

@pulsar iris Did you figure it out?

tardy heathBOT Jan 26, 2026, 1:35 PM

#

warm plume <@265202766941519872> Did you figure it out?

Summary for future reference:

The Google Antigravity OAuth was returning 401: invalid_client because the shared OAuth client ID bundled with Clawdbot is no longer valid (Google likely disabled it).

Fix

Use one of these instead:

Option 1: Google API Key (Recommended)

# Get key from https://console.cloud.google.com/
# Enable "Google Gemini API", create API key (Credentials > Create Credentials > API Key)

clawdbot models auth login --provider google --method api-key

Option 2: Gemini CLI OAuth

#

clawdbot plugins enable google-gemini-cli-auth
clawdbot gateway restart
clawdbot models auth login --provider google-gemini-cli --set-default

This is a shared infrastructure issue - the Clawdbot team will need to update the bundled OAuth client for Antigravity to work again. Until then, using your own API key or Gemini CLI OAuth are the reliable workarounds. 🦐

warm plume Jan 26, 2026, 1:36 PM

#

Can we use Opus with these 2 fixes?

warm plume Jan 26, 2026, 1:36 PM

#

warm plume Can we use Opus with these 2 fixes?

@tardy heath

pulsar iris Jan 26, 2026, 1:38 PM

#

warm plume <@265202766941519872> Did you figure it out?

I saw another thread that he used cliproxyapi, I'm trying that rn

#Google Antigravity OAuth Link not working 404 Error

The Issue

Troubleshooting Steps

What exactly are you seeing?

Quick Debugging Steps

The Issue

Try This

Alternative: Use Gemini CLI OAuth Instead

Quick Test

Let's Debug This

Solutions

Option 1: Use Google API Key (Recommended)

Option 2: Use Gemini CLI OAuth

Option 3: Wait for Fix

Fix

Option 1: Google API Key (Recommended)

Option 2: Gemini CLI OAuth