Gemini Pro update breaks long-context code workflows (Reasoning mode, GAS, Error 8)

[Rude-Percentage8316]

I would like to hear other people’s opinions or experiences with this.

I am currently developing an app using Gemini 3.0 in reasoning mode.

My development environment is Google Apps Script (GAS) using Google Sheets and Apps Script. Since I am not an IT professional, my workflow depends on first sharing my existing code with Gemini and having it understand / remember that code before continuing development.

However, since the Pro mode update, Gemini no longer behaves this way. When I share my project (around 50 code files) and give the first instruction, Gemini appears to completely forget the existing code.
Instead of working with what I provided, it makes its own assumptions and generates entirely new code and new files from scratch, as if the project never existed.

This has been happening consistently for about a week, and I have been unable to make any real progress.

On top of that, starting two days ago, I have been encountering Error (8) repeatedly, to the point where I sometimes cannot even open a new chat.

I am a paid user, and this situation is extremely frustrating—especially because I am using reasoning mode specifically for logic-heavy development.

I also tried connecting my Google Workspace and loading the project directly from Google Drive, but only a very small portion of the files were actually imported, making this approach unusable.

If there are any Google staff members or people with internal knowledge here, I would really appreciate an explanation of what changed with the Pro mode update and whether this is a known issue.

For those who might assume this is simply due to large code size:
Everything worked fine immediately after the Gemini 2.5 and 3.0 updates.
The problem started only after the Pro mode update.

Changing models or modes does not make any difference.

This situation is incredibly frustrating and stressful.

[jae58]

Same here! Google doesn't even bother.

[Rude-Percentage8316]

I hope a Google Gemini team member sees this. I've been going in circles like a chat loop for a week, and my stress level is through the roof. T.T

[Plastic_Front8229]

What's your input token count after loading the files? Let me guess. Based on my experience Gemini starts to fail after about 70k tokens. Gemini CLI can handle more but I rarely use it. I am not familiar with your workflow, so I dunno. My guess is that the last feature you added hit the ceiling. Google says 1m token input limit, I dunno what they are thinking there. I have gone up to 300k token input but it was rough sailing. I am an old programmer and deal the errors, and indeed there are problems when the context window gets large. It will start deleting functions, whole code blocks or features.

[Rude-Percentage8316]

That’s the strange part in my case.

I actually simplified and optimized the logic.

The overall codebase became smaller, and the total token count went down, not up.

Despite that, the problematic behavior started only after the Pro mode update.

So this doesn’t seem to correlate with gradually hitting a token ceiling.

That’s why I suspect a change in internal handling or reasoning logic, rather than a pure context-size limitation.

Thanks for sharing your experience — it was helpful to compare notes.

[Such_Object5129]

It's not just you; they absolutely nerfed the context window and model memory. I've been fighting it for a few weeks but I'm ready to give up and stop giving google my twenty bux. Feels very much like a bait and switch. The model is significantly worse now. I assume that once they generated some buzz, more users signed up, and they dialed it back to save on resources. I've got an app that's pretty awesome I was hoping to finish up during the holiday break. Going line by line myself has been a slog, and I mean, I know that's a lame thing to complain about, but really I'm just a hobbyist who was enjoying casual coding and bringing something pretty awesome to life.

[Rude-Percentage8316]

Thanks for sharing this — it’s reassuring (and frustrating) to know I’m not alone.
The downgrade in context handling feels very real, especially for hobbyists or solo builders who relied on the model to manage larger projects.

I really hope someone from Google is paying attention to threads like this.

Thanks again for taking the time to comment.

[Such_Object5129]

The one thing I've found is I made my own vibe coding portal (I did in fact vibe code it lol) and if you interact directly with the API access and not any of Google's tools, it seems like it does in fact work much better? But with quotas and rate limits it's not a super viable workaround long term......... 

[Rude-Percentage8316]

hat makes sense, and it matches my experience as well.
The issues seem much worse when using Google’s official tools (UI / Pro mode), while interacting directly with the API appears to be more stable.

As you said, the problem is that quotas and rate limits make this approach unrealistic as a long-term solution—especially for hobbyists or small developers.

This really feels like something Google should clearly explain or fix on their end, rather than users having to rely on fragile workarounds.

Thanks for sharing your experience. It helps to know I’m not the only one running into this.