We write on behalf of the Google AI Studio developer community—thousands of builders who were excited to adopt AI Studio and integrate it into real work.
Over the past weeks/months, AI Studio has become unreliable or unusable for many of us. The problems appeared around the Gemini 3.1 Pro rollout: persistent “quota exceeded” errors even under stated limits, blocked workflows, and linfinate build loops. Paid users are often the most impacted—willing to pay, yet unable to use the platform consistently.
At the same time, critical features have been removed without warning. Most notably, the ability to reset a conversation—a basic safety and reliability control developers depend on to prevent context contamination and hallucinations during testing and iteration.
What’s making this worse is the silence. The forum contains hundreds of posts reporting the same failures, yet there’s been little visible acknowledgment, no clear timeline, and minimal engagement.
We’re asking for immediate executive attention and action:
-
Stabilize AI Studio now (quota and access failures, reliability, billing anomalies).
-
Restore essential features, including conversation reset (or an equivalent control).
-
Communicate clearly—publish root-cause updates and realistic timelines, and engage the community.
-
If needed, re-staff or reinforce the team responsible so this gets resolved quickly.
We want AI Studio to succeed—and we want to keep building on Google. Please treat AI Studio as production-critical infrastructure for the developers who trusted it.
Sincerely,
The Google AI Studio Developer Community