OAuth Failed

[jaunty dock]

That error is coming from the provider side (Google’s “Cloud Code Assist” / Antigravity-style endpoint), not from Discord or your channel setup. A 403 “Verify your account to continue” usually means the Google account behind that OAuth token got flagged as needing verification (or otherwise restricted), so OpenClaw can’t make model calls with it.

A couple quick things to narrow it down + get you unstuck:

1. What OpenClaw version are you on?
   Run and paste:

openclaw --version

2. Confirm which model/provider you’re actually using
   Paste the output of:

openclaw models status

(or in-chat try /model status if your slash commands still work)

If you are using google-antigravity/... (most likely)

• Re-login the provider:

openclaw plugins enable google-antigravity-auth
openclaw models auth login --provider google-antigravity --set-default

• If it still returns 403, you’ll need to verify/unlock that Google account in the browser (Google-side). This is one reason the docs call out Antigravity OAuth as an unofficial integration that can hit account restrictions.

Fast workaround: switch to a non-Antigravity provider

If you have any other providers configured (OpenAI API key, Anthropic API key/setup-token, Gemini API key, etc.), switch your session/model using /model (pick from /model list) or set it via CLI (openclaw models set ...).

Docs that explain the provider differences + the Antigravity caveat:
https://docs.openclaw.ai/concepts/model-providers

If you paste openclaw models status + openclaw --version, I can tell you exactly which path applies.

[teal niche]

1. Version: 2026.2.21
2. Config : ~/.openclaw/openclaw.json
   Agent dir : ~/.openclaw/agents/main/agent
   Default : google-antigravity/claude-opus-4-6-thinking
   Fallbacks (5) : google-antigravity/claude-opus-4-6-thinking, google-antigravity/claude-sonnet-4-5-thinking, google-antigravity/gemini-3-pro-high, google-antigravity/gemini-3-pro-low, google-gemini-cli/gemini-2.0-flash
   Image model : -
   Image fallbacks (0): -
   Aliases (0) : -
   Configured models (6): google-antigravity/gemini-3-flash, google-antigravity/claude-opus-4-6-thinking, google-antigravity/claude-sonnet-4-5-thinking, google-antigravity/gemini-3-pro-high, google-antigravity/gemini-3-pro-low, google-gemini-cli/gemini-2.0-flash

Auth overview
Auth store : ~/.openclaw/agents/main/agent/auth-profiles.json
Shell env : off
Providers w/ OAuth/tokens (1): google-antigravity (1)

• google-antigravity effective=profiles:~/.openclaw/agents/main/agent/auth-profiles.json | profiles=1 (oauth=1, token=0, api_key=0) | google-antigravity:[e-mail]=OAuth ([e-mail]) [cooldown 1m]

Missing auth

• google-gemini-cli Run openclaw configure or set an API key env var.

OAuth/token status

• google-antigravity usage: gemini-3-pro-low 100% left ⏱4h 59m · gemini-3.1-pro-high 100% left ⏱4h 59m
  • google-antigravity:[e-mail] ([e-mail]) ok expires in 48m

[jaunty dock]

Yep — based on that models status, your whole stack is effectively blocked on Google Antigravity right now:

• Default + 4/5 fallbacks are google-antigravity/...
• The only non-antigravity fallback is google-gemini-cli/..., but it’s missing auth, so it can’t actually take over.
• Your Antigravity OAuth token is valid (“ok expires in 48m”), so this is not an expired-token problem — it’s the upstream endpoint returning 403 “Verify your account to continue”.

What that 403 usually means (in practice)

It’s a Google account restriction/verification gate against that Cloud Code Assist-style endpoint. OpenClaw can’t fix or bypass that from the client side.

Antigravity OAuth is also explicitly called out in the docs as an unofficial integration that can trigger account restrictions, so the pragmatic fix is: stop relying on Antigravity as your only provider.
Docs: https://docs.openclaw.ai/concepts/model-providers (see the Antigravity caution)

---

Fix options (pick one)

Option A (fastest): make your fallback actually work (Gemini CLI OAuth)

If you’re OK switching to Gemini via the CLI OAuth provider, authenticate it so the last fallback isn’t dead:

openclaw plugins enable google-gemini-cli-auth
openclaw models auth login --provider google-gemini-cli --set-default

Then set your default model away from google-antigravity/... (use /model list → pick a non-antigravity one).

Option B (recommended): switch to an official provider (API key / supported OAuth)

Set up any non-antigravity provider (Gemini API key, Anthropic API key/setup-token, OpenAI API key, Codex OAuth, etc.), then switch your default to that.

If you want Gemini (API key route): put GEMINI_API_KEY=... in ~/.openclaw/.env (since “Shell env: off”), restart the gateway, then /model list and choose a google/... model.

Option C: keep Antigravity, but you must fix the Google account

If you insist on google-antigravity, the next step is on Google’s side:

• sign into that account in a browser and complete whatever “verify your account” flow it’s demanding

• then re-run:

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

---

One question so I can give you the cleanest “do this, then this” sequence

Do you want your agent to keep using Claude specifically, or is switching to Gemini acceptable for now?

(If “Claude specifically”, then Option B with an Anthropic/OpenAI-style provider is the way out; Antigravity is the brittle path.)

[teal niche]

I wanna keep using antigravity, how do i solve the 403 error?

[jaunty dock]

You can’t “fix” that 403 from inside OpenClaw — it’s the Antigravity/Cloud Code Assist endpoint refusing your Google account. Your OAuth token is still valid, so this isn’t an OpenClaw auth-file problem; it’s an account verification / restriction on Google’s side.

What you can do (legit, non-bypass) is:

1) Verify what Google is actually blocking

Log into the same account ([e-mail]) in a normal browser and check for any of:

• “Verify it’s you” / phone verification prompts
• account security holds
• a banner saying the account/service is disabled/restricted

If Google has put the account into a ToS/restriction state, the only real resolution is Google account restoration/support (there’s nothing OpenClaw can send to make 403 go away).

2) Re-auth Antigravity after you’ve cleared the verification/restriction

On the gateway host, re-run the login flow to refresh what OpenClaw stored: