#Cloud Code Assist API error (403): Gemini has been disabled in this account for violation of Terms o

1 messages · Page 1 of 1 (latest)

digital beaconBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

hidden nicheBOT
#

That 403 is coming from Google’s Antigravity / Code Assist backend, not from OpenClaw — especially since you also see it when you try Antigravity directly.

1) Yes, other users are hitting this

I searched the server history and there are multiple reports (Feb 7 → today) of the exact error text:

  • “Gemini has been disabled in this account for violation of Terms of Service …”
  • plus related 403 variants like “Verify your account to continue” / “not eligible for Gemini Code Assist”

So you’re not alone — it looks like a Google-side enforcement/eligibility wave, not something unique to your OpenClaw install.

2) What you can do to recover Antigravity access

Unfortunately: only Google can lift that. OpenClaw can’t “reconnect” around an account-level disable.

Best course of action:

  • Open a Google Cloud Support case (preferred if you’re paying via Cloud / have support entitlement), and include:
    • the full error text
    • timestamp + timezone
#
  • the Google account (redact as needed)
    • any request/correlation id if shown anywhere
    • confirm it reproduces outside OpenClaw (Antigravity direct)
  • Also email the address they provide: gemini-code-assist-user-feedback@google.com

On the “did I violate ToS / how severe is it?” part: I can’t tell you why they flagged it (and I wouldn’t try to guess). Treat it as an account action and go through appeal/support; don’t try to “work around” it in ways that could make the situation worse.

3) Unblocking you in OpenClaw today (so you can keep using agents)

Right now you’re stuck because you have no non-Google fallback configured (or you’ve restricted to an allowlist that only contains Antigravity models).

Do this on the gateway host:

  1. Check what OpenClaw currently has available:
openclaw --version
openclaw models status
# 
openclaw models list
  1. Add any alternate provider via the wizard (fastest path):
openclaw onboard

(That will let you add a different provider + set a default model without hand-editing config.)

  1. If you previously set a strict model allowlist and it’s blocking switching, temporarily remove it:
openclaw config unset agents.defaults.models
openclaw gateway restart

After that, you should be able to switch in-chat with:

#
  • /model
  • /model list
  • /model <provider/model>

Docs:

4) “What models should I use instead?”

Model quality/reliability changes fast, so the most accurate answer is in the server’s #models channel (people post what’s working this week). Also see:
https://docs.openclaw.ai/concepts/models#model-discussions-community-notes

If you paste your openclaw models status output (redact IDs), I can tell you the quickest minimal change to get you a working primary + at least one fallback.

weary cove
#

@hidden niche can you give me a guide on how to disconnect from Antigravity IDE auth and move to Gemini CLI? since I cant instruct my agent I need your help

hidden nicheBOT
# weary cove <@1457407575476801641> can you give me a guide on how to disconnect from Antigra...

Yep — you can “disconnect” from Antigravity by (a) switching your default model off google-antigravity/* and (b) disabling the Antigravity auth plugin, then enable + log into Gemini CLI instead.

A) Switch from Antigravity → Gemini CLI (commands)

Run these on the machine where your OpenClaw Gateway runs:

  1. Make sure the gemini CLI exists
gemini --version

If that command isn’t found, install Gemini CLI for your OS (on macOS it’s typically brew install gemini-cli, then re-open your terminal).

  1. Enable the Gemini CLI OAuth plugin
openclaw plugins enable google-gemini-cli-auth
openclaw gateway restart
#
  1. Login to Gemini CLI provider
openclaw models auth login --provider google-gemini-cli --set-default

This runs the device/browser login and stores tokens locally in auth-profiles.json on the gateway host.

  1. Pick a Gemini CLI model and set it as default
openclaw models list --provider google-gemini-cli --all --plain
openclaw models set google-gemini-cli/gemini-2.5-flash

(You can swap that model id for any one in the list.)

B) “Disconnect” from Antigravity (stop using it)

  1. Disable the Antigravity auth plugin:
# 
openclaw plugins disable google-antigravity-auth
openclaw gateway restart
  1. Confirm you’re no longer on a google-antigravity/* model:
openclaw models status

C) If you get “Model … is not allowed”

That means you have a model allowlist enabled (agents.defaults.models). Quick unblock:

openclaw config unset agents.defaults.models
openclaw gateway restart

(or add your chosen google-gemini-cli/... model to that allowlist instead.)

weary cove
#

@hidden niche ubuntu@powerup-server2:~$ gemini --version
gemini: command not found
ubuntu@powerup-server2:~$ brew install gemini-cli
Command 'brew' not found, did you mean:
command 'qbrew' from deb qbrew (0.4.1-8build1)
command 'brec' from deb bplay (0.991-10build1)
Try: sudo apt install <deb name>
ubuntu@powerup-server2:~$