I’m experiencing the same issue, perhaps it’s related to google, because it doesn’t happen to me on other models like Claude or GPT.
1 Like
Same thing here. Absolutely useless now and burned through loads of requests
The video is all dialog one output at a time
Hey all, while we cannot initially see a cause for this degredation, it’s clear something is not quite right here - the team are digging into it, and we hope to get this ironed our as soon as possible.
We will continue to update you all here as and when we learn more on this issue.
Just to confirm, once the issue is resolved, we will be happy to refund any spent usage on Gemini while this issue is affecting users!
10 Likes
Oh my God.
It was so hard to work today, but I wasn’t the only one!
Looking at this, I rejected what I’ve been working on for hours today.
I don’t think I’m going to work more today.
I had many of these and it was weird…
I tried copying and pasting a few of these but I kept getting an error that I was pasting too much text
@danperks how do we reach out for a potential refund?
Action: Retry
gh pr createwith the title “feat-backend: Initialize Supabase Backend”.It seems the shell is now having trouble with the#1part of the title.Let’s try creating the PR with the title simply as
feat-backend: Initialize Supabase Backend. The body already includesCloses #1, which will correctly link the PR to the issue.Okay, it seems the shell is still having issues, likely with the#1in the title.I will remove the
(#1)from the title entirely. TheCloses #1in the body will still link the PR correctly.Retrying with the title
feat-backend: Initialize Supabase Backend.Okay, it seems the shell is still having issues, likely with the#1in the title.I will remove the
(#1)from the title entirely. TheCloses #1in the body will still link the PR correctly.Retrying with the title
feat-backend: Initialize Supabase Backend.Okay, it seems the shell is still having issues, likely with the#1in the title.I will remove the
(#1)from the title entirely. TheCloses #1in the body will still link the PR correctly.Retrying with the title
feat-backend: Initialize Supabase Backend.Okay, it seems the shell is still having issues, likely with the#1in the title.I will remove the
(#1)from the title entirely. TheCloses #1in the body will still link the PR correctly.Retrying with the title
feat-backend: Initialize Supabase Backend.Okay, it seems the shell is still having issues, likely with the#1in the title.I will remove the
(#1)from the title entirely. TheCloses #1in the body will still link the PR correctly.Retrying with the title
feat-backend: Initialize Supabase Backend.Okay, it seems the shell is still having issues, likely with the#1in the title.I will remove the
(#1)from the title entirely. TheCloses #1in the body will still link the PR correctly.Retrying with the title
feat-backend: Initialize Supabase Backend.Okay, it seems the shell is still having issues, likely with the#1in the title.I will remove the
(#1)from the title entirely. TheCloses #1in the body will still link the PR correctly.Retrying with the title
feat-backend: Initialize Supabase Backend.Okay, it seems the shell is still having issues, likely with the#1in the title.I will remove the
(#1)from the title entirely. TheCloses #1in the body will still link the PR correctly.Retrying with the title
feat-backend: Initialize Supabase Backend.Okay, it seems the shell is still having issues, likely with the#1in the title.I will remove the
(#1)from the title entirely. TheCloses #1in the body will still link the PR correctly.Retrying with the title
feat-backend: Initialize Supabase Backend.Okay, it seems the shell is still having issues, likely with the#1in the title.I will remove the
(#1)from the title entirely. TheCloses #1in the body will still link the PR correctly.
…
1 Like
Also can’t recommend SpecStory enough for helping to archive Cursor chats. I have no affiliation with the project, but a day like yesterday was a perfect day to have some logs 
1 Like
I’ve been using task-master and asking it to follow the task list. It was magical the other day. now it, as other have stated, goes into loops, it repeats the last thing i said to it at the start of every response, and most recently it has gone into a completely crazy text block.
request id:
47d1d690-1211-41d7-ab21-ddfd5094ebf2
Here is an example.
869a31aa-9955-4a08-8574-af71b8cde219
You see, a simple request caused so many advanced tool calls, about 20 times the amount I usually use. It’s really amazing. I have stopped using it. Has anyone encountered the same situation as me? I am also using gemini 2.5 promax, and it is much stupider than before. But thank God, someone has also discovered this problem.
1 Like
Please do not continue to use Gemini while this issue is ongoing, we will likely issue an automated refund within a set timeframe where we think users are affected.
Still working on root causing this and resolving!
5 Likes
yes, same thing for me. Racked up enormous amount of tool calls.
90ef8eca-508b-46f1-bdf8-b0db0b5ac416 , you can check this request id …
I have been waiting for a reply from Gemili. I think this should have happened yesterday, about 30 hours ago.
Do we have an ETA for when this is gonna be resolved ? I really needed to work on my app today since I am about to publish it for my client … 
Hey, we’re working with Google on this currently, but no major updates yet unfortunately!
2 Likes
Something wonky is happening on the claude-3.7-sonnet too, many times I am getting “No changes made” and it is just all weird and loops a lot… request 414d67cb-dbc9-4568-86e8-ac38400e5c1f
Everything started yesterday at the similar time
4 Likes
The outage coincided with Gemini releasing context cache. Might be related.
4 Likes