#This version of Antigravity is no longer supported. Please update to receive the latest features!
1 messages ยท Page 1 of 1 (latest)
This message is coming from Google's Antigravity service directly, not from Moltbot/Clawdbot. Google periodically deprecates older API versions and clients using them get this "no longer supported" message.
To fix this:
-
Update Clawdbot/Moltbot to the latest version:
cd ~/moltbot-ref && git pull && pnpm install && pnpm build -
Re-authenticate Antigravity (refresh the OAuth token):
pnpm clawdbot configureRe-select "Google Antigravity" to refresh the auth tokens.
The Antigravity OAuth flow may have been updated on Google's side, so the old tokens/credentials are now considered outdated.
Quick check: What version are they running? clawdbot --version (or moltbot --version)
If they're on an old version, that's almost certainly the cause โ Google retires API versions regularly.
2026.1.24-3
Version 2026.1.24-3 is from January 24th, so there are newer builds available. Google has deprecated that Antigravity API version.
Update steps:
cd ~/moltbot-ref
git pull
pnpm install && pnpm build
Then restart the gateway:
clawdbot gateway restart
After updating, re-run configure to refresh the Antigravity OAuth:
clawdbot configure
The new version should have the updated Antigravity API client that Google is now requiring.
im on windows powershell
That's the latest build on the github
not working
still the same problem
im going to change it to gemini key one and see if that works
Good plan! Using a direct Gemini API key is a solid alternative.
Model format for direct Gemini (not Antigravity):
google-gemini/gemini-1.5-progoogle-gemini/gemini-1.5-flash(cheaper/faster)
Make sure to set the GOOGLE_GEMINI_API_KEY environment variable or configure it via clawdbot configure.
This bypasses Antigravity entirely and uses your own API key directly. Just note that direct Gemini has its own rate limits and pricing, separate from the free Antigravity access.
โ ๏ธ Don't post API keys in Discord!
That key is now exposed. Anyone who saw it can use your Gemini quota/billing.
Immediately:
- Go to Google Cloud Console
- Find that API key and delete it
- Create a new one
- Only share it via DMs or secure channels
API keys in public chat = identity theft risk for your GCP account. Rotate it ASAP.
i didnt i just want to know which letter im looing on.. I
when i put in the API key, this is what sent to me LLM error: {
"error": {
"code": 400,
"message": "API key not valid. Please pass a valid API key.",
"status": "INVALID_ARGUMENT",
"details": [
{
"@type": "type.googleapis.com/google.rpc.ErrorInfo",
"reason": "API_KEY_INVALID",
"domain": "googleapis.com",
"metadata": {
"service": "generativelanguage.googleapis.com"
}
},
{
"@type": "type.googleapis.com/google.rpc.LocalizedMessage",
"locale": "en-US",
"message": "API key not valid. Please pass a valid API key."
}
]
}
}