Google Banned My Antigravity for Using OpenClaw

TL;DR: Be sure to remove your Antigravity/Gemini profiles from OpenClaw or MoltBot or ClawdBot. Otherwise, Google also bans Antigravity on the account itself. Instructions below for how to remove the plugin and revoke the OAuth token to lower the risk of Google banning antigravity on your entire account.

I had been hearing about people getting their Google antigravity banned because of the OpenClaw plugin for about a week. Not just the plugin getting banned from OpenClaw, but Google banning antigravity on the account itself. I figured it was only a matter of time before mine got hit too. Sure enough, it did.

Last week I asked Gemini thinking/pro for help removing it. It wasn't able to give me the full steps. This week I tried again, and it was better. I pieced together what it gave me into this comprehensive list without extra fluff.

Important: In openclaw.json, make sure you don't just delete the contents of the google-antigravity section. Delete the key and value entirely.

Full Removal Steps

A few notes before you start:

• If you don't have a GUI, use vim ~/.openclaw/openclaw.json and type :syntax on.
• If you are using VS Code for the edits, you have a massive advantage: if you make a mistake (like leaving a trailing comma or a dangling brace), VS Code will show a red squiggle. Don't ignore those red squiggles!
• Step 3: deleting local files doesn't stop Google's server from seeing that the token was "granted." Open https://myaccount.google.com/connections and remove "OpenClaw" or "Antigravity."

# Remove Antigravity from OpenClaw (Full Removal Steps)

# 1. Prep (doesn't hurt)
openclaw models status
openclaw gateway stop
pkill -f openclaw   # Force-kills any processes that are still running
ps aux | grep openclaw # Should return nothing but your grep command

# 2. The actual deletion (3 steps)
# Config Cleanup (Remove the 'google-antigravity' plugin and model references)
# IMPORTANT: Delete the entire google-antigravity key and value, not just the contents
code ~/.openclaw/openclaw.json

# This is where the actual OAuth tokens live
code ~/.openclaw/auth-profiles.json

openclaw plugins disable google-antigravity-auth

# 3. Revoke the token at the source (on Google)
# Open this link and remove "OpenClaw" or "Antigravity":
# https://myaccount.google.com/connections

# Optional: verify your JSON
python3 -m json.tool ~/.openclaw/openclaw.json > /dev/null && echo "✅ Config is Valid" || echo "❌ Config has a Syntax Error!"
python3 -m json.tool ~/.openclaw/auth-profiles.json > /dev/null && echo "✅ Auth is Valid" || echo "❌ Auth has a Syntax Error!"

# 4. Reset and Verify
openclaw gateway start
openclaw models status

Here is a command to just pause openclaw on the system, if this is on someone else's computer and you might want to install it again later using a different provider. The command will move the credentials to a backup file and then verify that openclaw is paused:

openclaw gateway stop; pkill -f openclaw; systemctl --user disable --now openclaw-gateway 2>/dev/null; launchctl bootout gui/$UID/ai.openclaw.gateway 2>/dev/null; mv ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.bak; mv ~/.openclaw/auth-profiles.json ~/.openclaw/auth-profiles.json.bak; echo "✅ OpenClaw Frozen. Credentials moved to .bak"
ps aux | grep openclaw | grep -v grep; ls ~/.openclaw/*.bak; [ ! -f ~/.openclaw/openclaw.json ] && echo "🛡️ Status: Safe. No active config found."

To resume openclaw, run the following command (but then make sure you remove the Antigravity profile from Google's connections!):

systemctl --user enable openclaw-gateway 2>/dev/null; launchctl bootout gui/$UID/ai.openclaw.gateway 2>/dev/null; mv ~/.openclaw/openclaw.json.bak ~/.openclaw/openclaw.json; mv ~/.openclaw/auth-profiles.json.bak ~/.openclaw/auth-profiles.json; echo "✅ OpenClaw Resumed. Credentials restored from .bak. Don't forget to remove the Antigravity profile from Google's connections in the credentials files!"

Once you have the right instructions, the actual removal takes about five minutes. But if you factor in the time spent getting those instructions (and verifying nothing was missed), it was closer to 25 minutes total.

The key step most guides miss is #2: cleaning out auth-profiles.json. That's the piece I couldn't find last week. Without removing those auth profiles, OpenClaw still has the credentials locally and will keep trying to use them. Revoking the token on Google's side (step #3) is helpful too. I saw that tip on a Reddit thread last week. But the auth-profiles cleanup is what actually unblocks things.

Keywords: openclaw antigravity banned, remove google antigravity plugin, openclaw google-antigravity-auth, openclaw.json cleanup, auth-profiles.json, revoke openclaw oauth token, openclaw gateway not starting after ban, openclaw models status error, google antigravity plugin removal guide, openclaw plugin disable