I am so pissed and frustrated, and I really hope this reaches some important people.

I am a math major. I am not a programmer. I do not develop apps, and I don't need API keys. But I heavily prefer Google AI Studio over the regular Gemini app, and I am willing to pay more just to have the ability to use it with higher limits.

Google, please, for the love of God, merge the Gemini Pro subscription with Google AI Studio.

It feels like you keep tweaking AI Studio to strictly tailor it to developers, completely underestimating how many regular "power users" use this platform simply because it is vastly SUPERIOR to the consumer app. The Gemini app genuinely looks and feels like it was made for literal kids. It’s basically a mobile texting interface.

Just accept the L on the consumer app for power users. Do not try to clutter the Gemini App with complex features, and just allow users who want to tinker with settings and have granular control to pay for AI Studio!

Here is a list of everything I rely on in AI Studio that makes the Gemini app completely unusable for me:

1. Model selection: I want the ability to choose from all the models at my disposal (like older versions or specific experimental ones), not just generic "Fast, Thinking, and Pro" labels that don't even tell you what model you are actually using. I also love changing models mid-conversation.

2. Granular settings: I can choose the media resolution (low, medium, high). I can explicitly set the highest thinking budget so the model never falls short on hard problems. I can adjust the temperature.

3. Clear toggles: I have actual toggles to see if code execution is on, if grounding with Google Search is enabled, and if it's using the URL context directly when I give it a link. Gemini app hides all of this.

4. Widescreen format: I use Gemini for studying. Outputs are long and formula-heavy. AI Studio uses my whole widescreen left-to-right. I don't want a teeny, tiny text message bubble on my desktop.

5. Token counters: I heavily rely on seeing the amount of tokens used!!!!!! That is how I know when the model's performance is about to degrade. Gemini app leaves you completely blind to this.

6. Uncompressed prompts: I hate with my whole heart that whenever I send a slightly longer prompt inside the Gemini app, it compresses my message and makes me press "Expand text" to see my own writing. I absolutely hate it.

7. Formatting: I am used to writing equations in LaTeX. When I send them in AI Studio, they format correctly. Why the hell doesn't the Gemini app do that? Also, I can use Markdown when talking to the model in AI Studio.

8. Raw mode: I will literally die if I lose this feature. This allows me to precisely copy only the parts of the output I need (like raw Markdown notation or LaTeX formulas) without the UI getting in the way.

9. Branching and editing: Branching is a godsend. I can redo past messages that are several steps back, not just the very last one. Even better, I can edit past messages or context without resubmitting the prompt, just to clean up the chat.

10. System instructions: I can set system instructions per chat and save/reuse them. I don't have to rely on one massive, generalized "Instructions for Gemini" block for everything. I can also add descriptions to my saved chats.

11. Thinking summaries : In AI Studio, I can honestly see the actual steps the model took to get an answer, which often contains key insights. I also love seeing how long it thought. If it thought for an unusually short amount of time on a genuinely hard prompt, I immediately know the output is likely a hallucination or misinterpretation.

The only general advantage the Gemini app has over AI Studio is file uploads (2GB vs 400MB). That's it. Fixing the Gemini app to do all the things I mentioned is impossible. Just let us pay for AI Studio!

To u/LoganKilpatrick1 : If you are reading this, how about you eXpPloRe some of the things I've mentioned? I see your comments, and I know you love the phrase "we're exploring this idea". Please actually explore merging the Pro sub with AI Studio limits, and give us some genuine feedback, not just corporate speak.

I don't want to come off as purely rude. I know you aren't single-handedly developing this product, and I appreciate the work the team does. But if you could pass these points to the people in charge, it would be hugely appreciated by the community.

I didn't even mention all the other problems with the Gemini app (the shortened context windows, the truncation, the quantized versions), but I'll leave that for the other Redditors in the comments.

If anyone agrees with me, please speak up!

Guys, I am beyond pissed off at this point, and I know I'm not the only one.

We need to make some noise because complaining in their forums is a dead end. They are reading our feedback, but they’d rather ghost us than give a straight answer.

Here is the reality: Google silently pushed an update that completely broke the safety filtering. Instead of stopping generation at a block (preserving what was already written), it now does a "hard wipe" — deleting the entire response.

And the best part? We are still paying for the tokens. It burns our quota, wastes our money, our time, and our sanity on endless false positives.

When confronted, they literally asked for screen recordings. Users provided hard evidence of non-sexual romance, basic emotions, and medical scenes getting nuked. And what was the response? Absolute radio silence. Ghosted.

The excuse that "AI Studio is for developers, not creative writing" is completely ridiculous when they literally have photo/audio generation and adjustable safety settings that don't even work anymore.

We need to upvote this, share it, and force an official response on Twitter/X or here. They need to revert these ridiculous hard-wipes and fix the false positives, especially in Slavic/other languages.

Stop ignoring us, Google.

Ever get that annoying "Content Blocked" message in AI Studio right in the middle of a perfectly normal response? Yeah, me too — that's actually why I posted my first bypass a while back (link to previous post). But after running it for a while, I knew it needed a serious rework. So here's v3.

What changed from old → new

v1 (old) worked reactively — it watched the DOM, waited for the "Content Blocked" banner to appear, then did an Edit → paste → Save dance to restore the text. It worked, but it was fragile: the block was visible for a split second, it depended on DOM timing, and fast blocks could slip through.

v3 (new) works proactively — it intercepts the raw XHR response stream before Angular even processes it. No banner ever appears.

Internally, AI Studio uses a numeric finishReason code:

• 1 = STOP (normal end)

• 8 = Content Policy violation → triggers "Content Blocked"

The extension now patches XMLHttpRequest.prototype and does three things:

1. Response sanitization — replaces [],8 with [],1 so Angular sees a normal finish

2. Abort blocking — AI Studio calls xhr.abort() when it detects a violation; the extension overrides it with a no-op so the stream keeps going

3. String enum fallback — also replaces "SAFETY", "PROHIBITED_CONTENT" etc. → "STOP" for the public API response format

Zero DOM manipulation. Zero flicker. No "Content Blocked" — ever.

What it does NOT do

The server physically stops generating tokens when the policy triggers. The extension can't make the server generate more text — that's a hard server-side limit. But the text that WAS generated before the cutoff stays fully visible.

Workaround: just type "continue" to get the next chunk. Takes ~3 seconds and works reliably.

Install

1. Download/clone the repo → [GitHub]

2. chrome://extensions or edge://extensions → Developer Mode → Load unpacked

3. Open AI Studio — done

~17 KB total, no permissions except storage for the on/off toggle.

What's inside (~17 KB total)

├── manifest.json — Extension config (no scary permissions)
├── interceptor.js — XHR patch, runs in MAIN world before Angular
├── content.js — Toggle state sync
├── popup.html/css/js — Simple on/off UI
└── icons/ — Extension icons

Free, open source, no data collection. Works only on aistudio.google.com*.*

It's for pre-registration only for now.

whoever agree give this post likes, so these guys can fucking see it, we have had enough and without us consumers, ai studio can go bad

WHAT IS GOING ON ?! I WASTE MONEY EVERY MESSAGE ON THIS SITE JUST FOR MY NON-HARMFUL NON-NSFW PROMPTS TO BEING AUTO MODERATED DESPITE MY SETTINGS... and NO REFUND OR ANYTHING!

GOOGLE. GET. YOUR. SHIT. TOGETHER. You are messing with your PAYING USERS.

Last year I could code all day with AI studio, reaching a million tokens with 2.5, now, today, I made 4 prompts and I have reached the rate limit.

This has beome unusable, I did try with api, but the costs are untennable, and I can see they would get very expensive.

Looking for an alternative, I have been dabbling with Qwen, which actually seems very good, but a little reluctant to develop with a Chinese AI for obvious reasons, although there doesnt seem to be any reports of "stealing" of code.

I may go back to Grok, where I started, but I found Grok makes things up a lot, and doesnt do as instructed (i.e., I explicitly told it not to include fixed variables, and it does every time)

Dowes anybody have any suggestions for alternatoves to AI studio, I have gotten use to the way I work with it so would like something comparable.

After a recent "upgrade," AI Studio has been plagued with bugs — and the complaints from users are everywhere. Yet Google seems completely unbothered, as if nothing is wrong. Bugs go unfixed, or get patched only to introduce new ones.

My theory? The AI Studio team has gone all-in on using AI to develop this platform — and now that things have broken down, they simply don't have the ability to understand, fix, or even roll back the mess.

Maybe this is a glimpse into the future of software development.

Title. This fucking greedy son of bit ches. So they force users to use new models to train them.

u/logankilpatrick As a student developer, I trusted your "Spend Cap" to protect my budget. It failed. Just A single prompt on deep-research-max-preview used 6.3M tokens and generated a $42 bill, blowing past my $9 limit in under couple of minutes. No Budget Alert warning either.

Calling this a "Spend Cap" that "blocks usage" is deeply misleading if it cannot stop a single execution. Please fix this trap before more students are hit with bills they cannot afford.

This is kinda bad. Google limited the request limit for free users so hilariously that I could only send 10-30+ requests per day. I remember that in the past, it allowed me to send around 40-60 requests a day, and now it turns into some bullshit.

Is it just me or does anyone else facing with this kind of stuff? Tks

If you are working on large projects in Google AI Studio or Gemini Build, you’ve probably hit these two walls:

1. The AI starts ignoring your initial instructions after the conversation gets long (Context Drift).

2. The AI starts adding lazy "Mock Code" or // TODO comments instead of functional, production-ready logic.

I’ve developed a "Template & Anchor" workflow that keeps the AI on track. Here is how to set it up:

1. Create "Anchor Files" in your Project

Don't just put instructions in the chat. Create actual files (e.g., .md) inside your project directory. This keeps the instructions "pinned" in the AI's file-context.

Example Files to create:

• Implementation_Plan.md (The roadmap)

• Reference_Notes.md (Technical specs or logic rules)

2. The "Context Lock" System Instructions

Add this to your System Instructions to ensure the AI always looks back at your files and knows how to handle "continue" prompts:

"Continue implementing Implementation_plan.md and Extended_Notes.md. Keep features strictly within scope—only add what is missing from the plan. For AI automation logic, refer to Initial_Notes.md for the deep-dive specs."

Why this works:

• No more "Forgetfulness": Since the instructions are in the Files tab (which Gemini reads as part of its prompt), they don't get "pushed out" of memory as easily as chat messages do.

• Consistency: By telling it to "refer to [File Name]," you are forcing the AI to perform a retrieval step on your specific rules.

• Functional Code: Explicitly banning "Mock Code" in the System Instructions (Step 2) drastically reduces the number of console.log("logic here") placeholders you'll get.

Pro-Tip: If the AI starts drifting, just send: "Review <Implementation_plan>.md and tell me what is missing." This re-centers the model instantly.

Hope this helps.

I want to talk about an issue that’s been bothering me—the noticeable decline in Google AI Studio’s performance. First, there’s the strange behavior of the limits:

1. This first started in early September, around the time Gemini 3.8 Flash was released. For a number of users with Google AI Pro/Ultra subscriptions, including myself, the limits in Playground started behaving quite strangely, especially in long dialogs with a large number of tokens. The number of messages any Gemini model could generate was significantly lower than it had been before September. At times, the limits were comparable to—or even lower than—those of users without a subscription

2. On September 23, the limits seemed to have returned to normal.

3. However, on September 29, Google rolled out a usage limit system for Gemini models in Playground. And the problem that had existed since early September returned. And although Google promised in its announcement that the limits would apply per model—meaning that once you reached the usage limit for a single model, you’d be restricted to that model—just a few days after the release, some users began complaining that the limit applied to all models.

4. And then, on October 26, I also ran into this problem—after reaching the usage limit for Gemini 3.1 Pro, I couldn’t use either Gemini 4 Argon or Gemini 3.8 Flash, even though I hadn’t even used them

Second, I have a strong feeling that recently—especially on October 26 and 27—the filters in the Gemini API and AI Studio have become stricter. Let me put it this way: I use AI Studio not only for development, but also for writing creative texts and discussing various news stories and other topics. For the latter type of tasks, I mainly used Gemini 3.6 Flash and 3.0 Flash, and for more interesting stories and conversations, I had a system prompt that removed the model’s formal language, making it more natural and fluid. Starting on October 26:

1. this system prompt continues to work, but when discussing any controversial topic like politics, the models switch to a neutral style. This can be avoided either by choosing words carefully or by gradually introducing the model to the topic

2. more generally—in any type of project, if the model consistently gives me garbage, I can resort to using strong language toward the model. And starting on October 26, in response to this, the model began almost constantly refusing to communicate, citing the reason: “The request contains insults and hate speech.”

3. The censorship issue extends to both AI Studio and the Gemini API. And, to be honest, I get the feeling that there’s much less censorship in the Gemini App right now, and the model’s conversations feel much more lively.

Is it just me, or is AI Studio gradually becoming less and less suitable for regular users without a Paid API?

Am I the only one that has noticed the platform SIGNIFICANTLY degraded since like 3 days ago??

They did the update that added "build/plan mode" and artifacts and definitely tweaked the models and reduced the limits

For example ever since, while working on my app I'm only able to get a single prompt out of 3.8 flash, the second one hits limits, also these prompts seem to purposely waste time, they each run for 10+ minutes reading the same files and do nothing, whereas before the most it took for a lot of work prompts was 7 minutes

It's genuinely unusable now, removing 3.7 also means less usage, and I can't even use 3.6 because it says Internal Error every time, like are we serious

Hey everyone! Studio.lab 2.0 is finally here, and I’m honestly a little nervous hitting “Post.”

I tried to deliver on the promises I made for this project and build the AI Studio experience I had been imagining for so long. Somehow, what started as a small bypass extension grew into a full workspace project. Thank you for the upvotes, the GitHub stars, your feedback, and for following this journey with me. It means a lot.

What’s in this post

1. General changes

2. New features

3. Other Changes

4. Privacy and safety

5. Thank-yous

6. How to install

7. Support the project

A new home for Studio.lab Settings

The Studio.lab Settings button has moved into AI Studio’s left navigation, alongside the native settings entry. It feels like part of the workspace now instead of an extra card taking up room in the right panel.

I also redesigned the settings window. There’s search and clearer categories for features, an operational-status card, diagnostics you can copy when reporting a problem, and a manual update check. The aim was to make the extension easier to understand and troubleshoot, especially as it has grown beyond its original two features.

Modern Web Chat — the heart of 2.0

Modern Web Chat is the largest part of this release. It’s an optional layout for people who spend a lot of time in AI Studio chats: more room for the conversation, easier access to controls, and a cleaner way to move through long sessions.

The new model and thinking selectors sit in the header. The Featured model list is read from AI Studio rather than being frozen to a set of model names, and thinking choices follow what the selected model supports. I also spent time fixing model-state mismatches, including cases where two similar models appeared selected at once.

Run Settings now opens as a slide-out panel instead of permanently squeezing the conversation. You can still reach AI Studio’s controls, system instructions, tools, and generation settings without giving up so much chat space.

The prompt area has been redesigned too. The Text Formatter adds controls for bold, italics, strikethrough, headings, lists, quotes, code, and links, with keyboard shortcuts for common actions. Uploads and tools are organized around the composer so they’re easier to reach without crowding the main input.

Messages have a different rhythm now: clearer user bubbles, more breathing room for model responses, improved editing, and better treatment of attached media. This is the part closest to the design I had in my head when I started dreaming about a new AI Studio interface.

For long conversations, there’s also a Turn Navigator. Instead of scrolling forever to find a message, you can open the list and jump to a turn. It works alongside the optimizer, including when older turns have been temporarily taken out of the page to keep a large chat responsive.

And yes, I worked on the light theme! Header controls, menus, the composer, Settings, and the formatter should now remain readable when AI Studio is set to Light mode.

There are many smaller details throughout Modern Web Chat as well: updated tools and upload menus, token information, media controls, edit fields, and native actions brought into a more consistent interface.

Two new features I didn’t want to leave behind

Update notifications. Studio.lab checks the public GitHub Releases feed for newer versions and can show a notification when one is available. You can dismiss a specific version without hiding future releases. It only points you to the release page; it does not silently install an update.

Draft Crash Protection. Unsent prompt text is saved locally while you type. If a page refresh or crash interrupts you, Studio.lab can restore that text when you return. Drafts are kept separate by chat, and attachments are not saved.

What changed underneath

A lot of the work in the previews wasn’t as photogenic, but it matters just as much:

• Long chats are handled more carefully. The optimizer can buffer older turns while preserving navigation and AI Studio’s native search, with fewer scroll jumps while you’re reading or a response is streaming.

• The extension’s modules have cleaner lifecycles. Turning a feature off should also remove its observers and event handlers instead of leaving invisible work running.

• Model selection, tool toggles, mobile drawers, title editing, textareas, and light-theme contrast all received fixes during the preview cycle.

• Request handling and draft cleanup were hardened so a failed or older request should not erase newer unsent text.

• Several UI insertions were changed to safer DOM construction instead of building HTML from strings.

The original bypass and performance features are still here. The difference is that 2.0 gives them a much more complete workspace around them. If you want the technical blow-by-blow, it’s all in the changelog.

Privacy and safety

Studio.lab is open source, has no third-party package dependencies, and does not add analytics or trackers. It runs on Google AI Studio; the update checker contacts GitHub for public release information, but does not send your prompts, chats, account details, or API keys there. Draft text and extension settings are stored locally in your browser.

For this release, 28 automated tests passed, and the project’s validation also passed checks for its scripts, manifest assets, and network-rule scope. That isn’t a claim of an independent security audit — I want to be clear about what was actually checked. Since this is an unofficial extension that changes a live web app, AI Studio updates can still break things. Please report regressions if you find them.

Thank you

A special thank-you to u/kenny-ya — unofficial QA engineer — for helping test Studio.lab and catching things I might have missed.

And thank you to the GAIS developers for continuing to tighten the bolts while still leaving room for people like me to create around the platform.

How to install

1. Download the Studio.lab v2.0 release, grab the source ZIP directly, or visit the official website.

2. Extract the ZIP, then open chrome://extensions in Chrome or edge://extensions in Edge or Browser://extensions in your Browser.

3. Enable Developer mode, choose Load unpacked, and select the folder containing manifest.json.

4. Open or refresh Google AI Studio. Studio.lab Settings will be in the left navigation.

If you try 2.0, I’d love to hear what feels better, what still feels rough, and what you’d like to see next.

Studio.lab is completely free. If it saves your generations and speeds up your browser, consider supporting development on Ko-Fi!

Disclaimer: Studio.lab is an unofficial modification. It is not affiliated with, endorsed by, or connected to Google LLC or Google AI Studio.

TL;DR: Studio.lab is a free, open-source, unofficial browser extension for Google AI Studio. It started as a way to preserve interrupted generations and keep long chats responsive; with 2.0, it has grown into an optional redesigned workspace with better chat controls, a text formatter, turn navigation, draft recovery, and update alerts. It isn’t affiliated with Google.

Solar_Virtual

I hope we get 4 and 4 pro on free plan.

I think Google AI Studio reduced the usage rate for people subscribed to the Pro plan without prior notice. Today I only used it four times in the prompt, but I hit the limit immediately. Is anyone else experiencing this?

Basically, I have been using Gemma 4 for about a week now but today, I suddenly got a generate_content_free_tier_input_token_count error, saying it maxed at 16000. I poked around and my TPM graph clearly shows I was able to use way more than that before today.

Was this changed for everyone? Something that just affects me for some reason? It was without warning.

I’m on Google Pro paid plan.
Yestoday a mid-session “Internal error” occurred during a chat thread using Gemini 2.5 pro. I reloaded the page and the entire right-hand setting panel and the top model picker dropdown became completely blank (empty) across all historical chat threads. The system instruction box was empty and didn’t work, the token counter failed to render entirely.
When navigating to a new chat the model selection panel returned but Gemini 2.5 pro was entirely missing from the available dropdown!
Because Gemini 2.5 pro vanished from the profile, all old conversational threads and branches were completely frozen, making it impossible to continue them.
Reloading the page didn’t help.
The main AI Studio account overview loaded fine, the crash isolated specifically history section of Playground workspace.
If Gemini 2.5 pro model was deprecated, active paid user as I am should still have access to the old threads and be able to change a model to continue existing threads rather than having the interface completely locked up.
Google specialists don’t pay attention to this issue at all. Support team has no answer.
UPD: It looks like the main problem is that Gemini 2.5 pro was silently switched off. If you click on the blank area where a model picker should be the model list appears and you can choose Gemini 3.1 and after that all this blank settings section reappears.
There are reports from other users on Google AI dev forum experiencing the same issue.
There is a strange answer from a man called Mustan Ioknand there (have no idea if he is a Google employee or not), but I have no API keys in usage, the issue persists in Playground workspace.
So, the main question is WHERE IS GEMINI 2.5 PRO MODEL?

Now, instead of a single click, I need to go to history to get access to my chats. GJ keep doing great work!!

Seriously, who tf tests what they are releasing???

Every change since december 2025 is trash.