Cursor used to hide Gemini 2.5’s CoT under an expandable. In tasks where thinking mode first created a plan and is following the plan, this is really crucial since the CoT maintains the latest version of the plan in context, without the user (me) having to re-read the whole plan as it moves through the plan.
Since yesterday evening (basically after the 2nd 0.49 update was released), the entire plan is repeated every time agent goes to think and comes back. So during a task where the Agent had to think 14 times, I see 14 versions of the already verbose plan without an option to hide it.
Gemini is already quite verbose compared to Sonnet 3.7, which is a good thing when working in YOLO mode because I can basically keep reading the output and only expand the plan once in a while. This “bug” made it impossible to follow Gemini since the output is now 10s of pages long for a complex task.
I also noticed Gemini 2.5 performance dropped considerably at the same time. I think (or speculate) this has to do with the very verbose CoT that now leaks into the context, decreasing the SNR of the overall execution, hence confusing the model from identifying the right next step. The performance difference between the yesterday and before is so big that I basically cannot use gemini 2.5 when it used to be my default model before.
Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:
Check the forum to ensure the issue hasn’t been reported already: No
Provide a clear description of the bug: see above.
Explain how to reproduce the bug (if known):
Just use Gemini 2.5 in thinking mode for a task that will require planning first, then running a terminal command, checking its output, make a decision according the output and iterate over the plan.
Attach screenshots or recordings (e.g., .jpg, .png, .mp4).
Confidential so I cannot share, but basically, a single prompt causes a 40+ page (in Google docs) output with the same 4 step plan repeated 10+ times.
Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x). :
Mac OS X Sequoia 15.3.2.
Tell us if the issue stops you from using Cursor:
It stops me from using Gemini 2.5. Combined with the fact that Sonnet 3.7 thinking usage-based requests started charing 2 requests instead of 1 (*), this is a pretty bad regression IMO.
(*) I reported this to [email protected] recently. I am not complaining about pricing changes - I am just surprised there was no headsup, nor an update on the pricing page.
