You are seeing Gemini blocked inside Antigravity IDE and Gemini Code Assist returning a 403 error. The fastest way to restore access is to request a review from the Gemini Code Assist team and rule out local sign in issues.
Gemini disabled in Antigravity IDE and Code Assist shows 403
Antigravity shows an account setup failure with the message “There was an unexpected issue setting up your account. We apologize for the inconvenience. Please try again later.” and prompts you to sign in with a different account.
At the same time, Gemini Code Assist returns “Cloud Code Assist API error 403 Gemini has been disabled in this account for violation of Terms of Service.”
If you are also chasing recurring Antigravity setup or runtime failures, see this practical breakdown of error patterns and quick tests here common Antigravity error fixes.
Solution Overview
Aspect
Detail
Root Cause
Account flagged for a Terms of Service violation which disables Gemini features for that account
Primary Fix
Submit an appeal to the Gemini Code Assist review channel and re try clean sign in after account is cleared
Complexity
Easy
Estimated Time
10 to 20 minutes to submit review plus review time by Google
Restore access to Gemini Code Assist and Antigravity
Step by Step Solution
1. Submit an appeal to the Gemini Code Assist disablement team
This 403 is enforced server side. Local changes will not re enable access until Google clears the flag.
Send an email to the review channel with complete context
– Address: gemini-code-assist-user-feedback@google.com
– Include the exact errors, timestamps with timezone, your Google account email, IDE name and version, and any request IDs from logs if present
Use this template and paste it into your email client:
Subject: Appeal request: Gemini Code Assist disabled on my account - 403 ToS
Hello Gemini Code Assist review team,
My personal Google account cannot use Antigravity IDE and Gemini Code Assist.
Errors observed:
Antigravity setup: “There was an unexpected issue setting up your account. Please try again later.”
Code Assist: “Cloud Code Assist API error (403): Gemini has been disabled in this account for violation of Terms of Service.”
Account email: <your Gmail address>
Approximate time first observed: <YYYY-MM-DD HH:MM TZ>
Region and IP: <City, Country, public IP>
IDE and plugin versions: <VS Code or JetBrains version, Cloud Code version>
Any recent changes: <e.g., new project, new plugin, VPN change>
I use this only for personal development and will follow all Terms of Service.
Please review and advise how I can restore access or become compliant.
Thank you
<Your name>
2. Collect supporting logs and screenshots
Provide short and clear evidence. This helps reviewers quickly locate the offending event and verify compliance.
VS Code
– Open View then Output
– In the Output dropdown choose Cloud Code
– Copy the last 200 lines around the error and paste into the email or attach as a text file
JetBrains IDEs
– Open Help then Show Log in Finder or Show Log in Explorer
– Attach the latest idea log files and a screenshot of the dialog that shows the error text
If you suspect rate or quota effects in Antigravity, we documented quick checks here Antigravity quota trigger checks.
3. Confirm eligibility and policy compliance
Confirm you meet product availability conditions such as supported region at Available regions and age requirement for Gemini features
If anything may have triggered the flag, state in your email what changed and how you corrected it.
4. Retry a clean sign in after submitting the appeal
Refreshing tokens does not bypass a disablement but it removes local auth noise that can confuse testing after clearance.
VS Code
– Open the Command Palette and run Cloud Code Sign Out of Google
– Then run Cloud Code Sign In to Google and finish the browser flow
JetBrains
– Open Tools then Cloud Code then Sign Out
– Sign in again with the same account
Also confirm your active account in Cloud SDK if installed:
gcloud auth login
gcloud auth list
Open Antigravity again and attempt setup with the same account after you receive confirmation that access is restored.
5. Test with a different Google account
If a second account signs in successfully and Code Assist works, your original account is still blocked and requires review. This isolates the issue to account status rather than network or plugin.
6. Follow up if no response
If you do not receive an acknowledgment in a few business days, reply to the same thread briefly with your original ticket context and add any new evidence such as a fresh timestamp and screenshot.
For recurring service constraints after re enablement, see quota related notes here Antigravity quota considerations for Gemini.
Alternative Fixes and Workarounds
Use Gemini on the web while you wait
You can keep working with prompts at Gemini on the web until Code Assist access is restored
Try a different account for coding tasks
If you have a second compliant account, sign in with that account in Antigravity and your IDE to continue development temporarily
Reinstall or update the IDE plugin
Update Cloud Code to the latest version from the Extensions or Plugins panel
Restart the IDE and re test after sign in
This will not clear a policy block but can fix unrelated local issues encountered during review
Troubleshooting Tips
Check for VPN or network egress tools that might trigger policy checks
Capture exact error strings with timestamps and attach to your appeal
In VS Code, also open Help then Toggle Developer Tools then Console and copy any auth related errors
In JetBrains, check the Event Log tool window for errors tied to Cloud Code
If your account is part of a managed family or school program, confirm there are no content controls on AI features
New projects rarely affect this error, but you can still test a clean Google Cloud project to rule out project scoped policy prompts in the IDE
Keep IDEs and Cloud Code updated so auth flows and scopes are current
Avoid prompts that request disallowed content or abuse prone automation
Use clear, bounded tasks and avoid high frequency automated prompting that can resemble misuse
Maintain accurate Google account profile details and keep two step verification enabled
If you use multiple accounts, label them in your IDE and Cloud SDK to avoid accidental cross account activity that may look suspicious
Review quotas and service limits during heavy development periods to prevent noisy failures that complicate diagnosis. For a quick refresher on Antigravity quota behaviors, see this field note Antigravity quota reference.
Final Thought
A 403 Terms of Service disablement is enforced at the account level, so the only reliable fix is an appeal to the Gemini Code Assist team. Send a clear request with evidence, refresh your sign in, then re test. This usually gets you unblocked with minimal back and forth.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
