Antigravity access disabled account-wide (403 permission_denied) — requesting manual review

Google Antigravity
1

Hello,

I’m requesting a manual review of what appears to be an account-level restriction on Antigravity (antigravity-preview-05-2026 via the Interactions API), separate from a project closure I’ve already appealed.

Background: One of my GCP projects, gen-lang-client-0756621..., was closed by Trust & Safety for hosting content flagged as phishing. That flag was against a Firebase Hosting deployment of a school programme tracker (“Engaged Scholar”) that I’d shared privately with one family member. It authenticates via Firebase Auth using Google/Microsoft OAuth — the page never collects a password or any credential directly, which I believe is what triggered an automated phishing classifier (an unbranded *.web.app domain serving a sign-in page reads as a lookalike login to that kind of system, even though no credentials are actually captured). The hosting content itself is already gone — I can see it now 404s.

The problem I’m raising now: since then, every call to the Antigravity agent (antigravity-preview-05-2026) fails with:

{"error":{"message":"The caller does not have permission","code":"permission_denied"}}

This is happening across every GCP project on my account — including projects that have nothing to do with the flagged content, including a brand-new project I created today specifically to test this. I’ve confirmed:

  • The same API key works fine for standard generateContent calls and for the Deep Research agent — only Antigravity fails.
  • Billing tier isn’t the cause (tested on both prepay and postpay).
  • This isn’t project-specific — it fails identically on old projects and on a project created today that never touched the flagged content.

Given the Antigravity Agent documentation states it’s available “for both free tier and paid tier projects” with no enrollment/allowlist step, and given the consistent failure across unrelated projects, this looks like an account-level restriction on the Antigravity entitlement specifically, likely applied alongside the project closure above rather than a separate issue.

I’d appreciate a manual review of this restriction. I rely on Antigravity for a production app (a teacher planning tool, not related in any way to the flagged project), and would like to understand what’s needed to restore access — whether that’s this review, or something else I should be doing differently.

Thank you for your time.

2

Hello @David_Goh,

Thank you for following up and providing additional context regarding your account restriction.The account-level 403 permission_denied error on Antigravity is directly tied to the active Trust & Safety suspension on your associated GCP project (gen-lang-client-0756621599). Antigravity access will remain restricted until the underlying Trust & Safety flag is officially resolved.
To resolve this issue and restore your account access, please follow these steps:

  • 1. Resolve the Trust & Safety Appeal First

You will need to wait for the official review of your Trust & Safety appeal regarding project gen-lang-client-0756621599.
Appeal Tip: In your appeal submission, explicitly clarify what you noted on the forum—that the flagged Firebase page was a legitimate OAuth authentication screen (Google/Microsoft) and was not harvesting or collecting raw user credentials.

  • 2. Confirm the Flagged Content Returns a 404

To ensure the appeal can be processed smoothly, verify that the flagged URL (on *.web.app or *.firebaseapp.com) has been completely removed. You mentioned this is already returning a 404, which is the correct setup for review.

  • 3. Re-sync & Escalation Timeline

Once the Trust & Safety team reinstates project gen-lang-client-0756621599 and removes the phishing flag from your account, the restriction on Antigravity should automatically clear within 24 to 48 hours.

If you are still blocked after 48 hours: If your project is successfully reinstated by Trust & Safety but you continue to experience the 403 permission_denied error in Antigravity past the 48-hour mark, please reply directly back to this forum thread with proof of your successful appeal reinstatement.

3

Hi Ritesh, thanks for the reply.

I don’t think “wait for the official review” applies any more, I think the review has already happened. I received a message on 30 July (Google Cloud Console Appeal Notification 65158740…) stating the project will remain closed due to Terms of Service violations. I then shut the project down myself on 1 August since I no longer needed it, but that 30 July message reads as the appeal already being decided against me, not still pending.

Given that, could you clarify:

  1. Is there a route to submit a renewed or escalated appeal against that 30 July decision?
    1. Is the Antigravity account-level restriction tied specifically to that project’s Trust & Safety flag, or is there a separate account-level flag that needs its own appeal? I ask because the restriction is affecting every project on the account, including ones created after the flagged project was shut down.
  3. Happy to provide any further evidence needed (code, screenshots of the OAuth flow, etc). Thanks again for your help.
4

Also, is there a Google staff member or Trust & Safety team representative able to look at this directly? I don’t want to keep going back and forth on assumptions, given the previous reply suggested the appeal was still pending when it had actually already been decided against me by that point. Happy to provide the appeal case number, project ID and any logs needed if someone from the team can pick this up.