I am an individual developer using a personal Google Cloud project for educational purposes and personal productivity automation.
Recently, my project (ID: rising-fact-p41fc) was suddenly disabled due to an alleged violation of the Terms of Service (Status: 403) while I was actively using the Gemini API with the “OpenCode” AI agent.
I have already sent a formal appeal email, but I am posting here to request a manual review as I believe this was an automated false positive. I have had no intention of abusing the service and wish to ensure my environment remains fully compliant.
[Technical Debug Log] The service was interrupted with the following error details:
It has been 3 days since I posted this, but I am still unable to access the service. I would like to provide additional evidence that this is likely a system-wide false positive rather than a simple configuration error.
Paid Subscription: I am a current Google AI Pro subscriber. I am paying for a service that I cannot use at all due to this 403 error.
Official IDE Failure: Even when I attempt to use the official Antigravity IDE (antigravity-ide.com), I receive the following error: “There was an unexpected issue setting up your account.”
No Response via Email: I sent a formal appeal to gemini-code-assist-user-feedback@google.com 3 days ago, but there has been no feedback yet.
As a paying customer, I find this service disruption very frustrating. I am simply trying to use the tool for personal productivity automation as intended.
Could a Google representative please prioritize a manual review for my project (ID: rising-fact-p41fc)?
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
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.