Google Antigravity, Gemini Cloud Code Assist

Antigravity "Verify your account to continue" — what it means and how to fix it

{"error":{"code":403,"message":"Verify your account to continue.","status":"PERMISSION_DENIED"}}

What does "verify your account" mean?

Google's anti-abuse system has flagged the account and put a human-verification gate in front of it. It is not a quota problem and it will not clear on its own — every request on that account returns 403 until you complete the check Google is asking for.

Why does it happen?

It usually follows a burst of automated traffic, signing in from a new network or region, or an account that has never been verified with a phone number. Running several accounts from one machine makes it more likely, because the requests share an IP.

How do I fix it?

1. 1

   Open the verification URL Google returned — kRouter surfaces it as a clickable link on the connection card, so you do not have to dig it out of the raw error.

2. 2

   Complete the check in a browser signed in as that Google account. It is usually a phone or identity confirmation.

3. 3

   Back in kRouter, click Test connection on that account. A successful call clears the ban flag and returns it to rotation immediately.

4. 4

   If the account stays blocked after verifying, it has likely been suspended rather than gated — see the suspended/disabled guide.

Is it really this error?

These get mistaken for each other, and chasing the wrong one is where the time goes.

What will not fix it

Reasonable-sounding fixes that do not apply here — worth ruling out before you spend an afternoon on them.

• Retrying, or waiting for it to clear.

  There is no cooldown behind it. Every request returns the same 403 until the check is done.

• Re-authenticating the OAuth connection.

  The token is valid — that is why you get 403 rather than 401. New tokens hit the same gate.

• Switching to a different model on the same account.

  The gate is account-wide, not per-model.

What kRouter does automatically

kRouter locks the ENTIRE account for 24 hours — every model on it, not just the one you asked for. It immediately fails over to your next connected account or provider, so the request still completes. The account is flagged as needing human action and stays out of rotation until you fix it upstream.