After the latest update to version 2.3.41, cursor is behaving strangely.
After giving it the prompt, it starts writing its own thoughts… as if it were creating a plan… and it goes on for a long time, then starts writing, then stops again and writes its own thoughts (thinking, planning, next move, etc.).
I’ve been using cursor for a while, always with the same templates set. The prompts I write are always the same. I work in auto mode and I’m sure I’m not in plan mode (also because in that mode it creates actual plans and I know how to use it). In short… I haven’t changed anything in any settings. As it is now, it’s impossible to work.
A 30-second change takes 10-15 minutes.
I tried downgrading to previous versions, but the problem persists and it seems strange to me… it’s as if a mode has been implemented regardless of the versions. I’m asking for help because I’m stuck like this.
I need to find alternatives to cursor.
hi @ESTETICSUN_4 sorry to hear about the issue. Please help us understand where things go wrong or if this happens due to an update.
Could you post a full separate Bug Report with more info Create Bug Report
Also add a Request ID with privacy disabled so we can look into the details? Cursor Docs
I can’t create a bug report because it’s not a bug. It just works like this. It’s the way cursor behaves every time I give it a prompt.
It doesn’t change even if I downgrade.
Cursor itself doesn’t find anything wrong with itself.
I’m seeing the same thing and it’s not something you changed. Since the 2.3.41 update, Cursor sometimes shows its internal thinking even in auto mode. Downgrading doesn’t help because this behavior is server side. The only real fix is sharing a Request ID with the Cursor team so they can address it.
I admit I’m not very experienced.
Can you tell me how to do it?
I can’t work this way.
I don’t know if others have the same problems as me, but it’s really impossible.
Something like this?
I had it for a few hours late last night (20-01-26) only when using Composer.
I opened a new chat.
Yes, the site uses CPU power. The main source is DatabaseStatusIndicator updating the time every second. Optimizing it to reduce CPU usage:
Optimizing the component to reduce CPU usage:
Optimizing the component to reduce CPU usage:
Yes, the site uses CPU power. The main source is DatabaseStatusIndicator updating the time every second. Optimizing it to reduce CPU usage:
Optimizing the component to reduce CPU usage. The main issue is the 1-second time update interval. Here’s the optimized version:
Optimizing the component to reduce CPU usage. The main issue is the 1-second time update interval. Here’s the optimized version:
Yes, the site uses CPU power. The main source is DatabaseStatusIndicator updating the time every second. Optimizing it to reduce CPU usage:
Optimizing the component to reduce CPU usage. The main issue is the 1-second time update interval. Here’s the optimized version:
Yes, the site uses CPU power. The main source is DatabaseStatusIndicator updating the time every second. Optimizing it to reduce CPU usage:
Yes, the site uses CPU power. The main source is DatabaseStatusIndicator updating the time every second. Optimizing it to reduce CPU usage:
Indeed I have the same behaviours for now several days, but it’s quite “new” (since mid january 2026)