Google AI Studio Build Mode: Persistent "Permission Denied" Error — Cannot Edit Existing Project

Subject: Urgent — Persistent Permission Denied Error in Google AI Studio Build Mode — Existing Saeva.ai Project

Hello Google AI Studio Support Team,

I am developing an existing citizen services web application called Saeva.ai using Google AI Studio Build Mode.

My project was previously working, and I successfully made many changes. However, Build Mode has now stopped executing every prompt.

The exact error is:

“Permission denied. Please check your account permissions and project settings.”

Gemini requests are cancelled immediately.

Troubleshooting already completed:

  • Refreshed Google AI Studio.

  • Started a new chat inside the existing project.

  • Tested simple diagnostic prompts.

  • Retried the requests.

  • The error still persists.

Important details:

  • Existing project: Saeva.ai

  • Current free hosting hostname: saevatokashmir.ai.studio

  • The application preview is accessible.

  • Build Mode cannot execute prompts or modify files.

  • I have not purchased or connected saeva.in.

  • I need to preserve all existing source code, Firebase configuration, Firestore data and application functionality.

Please investigate whether this is caused by:

  1. AI Studio Build Mode project permissions.

  2. Project workspace authorization.

  3. Build agent backend failure.

  4. Applet or project snapshot access problems.

  5. Account-level restrictions.

Please help restore editing access to my existing project without resetting, deleting or recreating it.

I can provide the Applet ID, error screenshots and browser console logs privately.

Thank you.

Hello @Sahil_Abass,

Our records indicate the “Permission denied” error on your app cleared shortly after you posted, and Build Mode prompts ran again after that.

Your later prompts reached the Build Mode usage limit (“Quota exceeded”). Please wait a while, then try again in a new chat.

If publishing your app shows a build error about __dirname in your Vite config, you can ask Build Mode to use import.meta.dirname instead, then publish again.

Please let us know if you still see the “Permission denied” error.