RGENT: Antigravity Access Disabled (403 Error) - Requesting Manual Review

, ,

Hello Google AI Team,

I am writing to request a manual review of my account. When I try to log into the official Google Antigravity client, I keep getting an “Unexpected issue setting up your account” error, and my backend logs show a 403 Permission Denied related to the Cloud Code Assist API.

I realize now that this was likely triggered because I recently experimented with a third-party CLI tool (“OpenClaw”). I genuinely did not know that routing my authentication through this tool to access the API violated the Terms of Service regarding quota or acceptable use.

I am an active user with Pro subscriptions and heavily rely on your official services for my daily development work.

Actions I have taken:

  1. I have immediately stopped using all third-party CLI tools.

  2. I have gone into my Google Account settings and completely revoked all third-party application permissions and connections related to this.

  3. I have cleared all local Antigravity app caches.

Could you please help review my account and restore my access? I assure you that moving forward, I will only use the official Antigravity client and adhere strictly to the ToS.

Thank you for your time and help.

Contact Support. This forum is not Support.

Thank you for the reply. However, I don’t konw how to find support :sob:

Thank you for the reply.

unfortunately you belong to users that got ban, just like I did and many others did. Check this out : Gemini API Access Disabled (403 ToS) After Using OpenClaw Agent — Appeal Pending

Good luck!

Hi all,

We have heard your feedback regarding recent bans linked to third-party tool usage. We are currently rolling out a system-wide automated unban for all affected accounts. We appreciate your patience as we work to enhance the Antigravity experience. #terms

Hello @taffy_ace @K8L,

Following up on this thread—are you still experiencing these account bans, or have your Pro accounts been restored? Please let us know if you are still locked out so we can track if this issue is ongoing.