After using 0.46+ for a while, a lot of bad stuff happened that made me revert to version 0.45. Many people have had the same experience as me.
What do you think about this idea:
I think Cursor should fork a version from 0.45 to fix bugs and release it as LTS, only fixing bugs and not breaking the core features.
great idea, so far 0.45 is the most stable compared with 47 and 46
I agree with both hands! Cursor 0.45 is still the most reliable experience in my workflow. Small updates like improving the UI (thinking) will make it completely beat 0.46+
Agree!
Hey, could you describe which features you think should be brought back or improved? I’ll report this to our team.
UI: Most people are used to the 2 tabs for chat and composer. They know when to use chat and when to use composer. You can use chat and composer at the same time without having to review the chat history.
The UX of the bubble is also easier to see than 0.46.
Agent: I’ve noticed that the 0.45 agent is simpler but more suitable for devs. They can make decisions. It seems like 0.46+ agents make more decisions themselves, leading to Vibe coding, which is a buzzkill for technical people. Their advanced intervention capabilities are reduced.
btw, 0.45 feels more stable and secure to work with. I’m not sure why, maybe it’s the familiarity and control.
In 0.47, beta features enabled, you can create many modes with many tools enabled. Agent has all of them, but you can restrict search, internet, docs, editing, tools and create your own mode without forcing a prompt.
agree.
And even the non-tech people who think this is going to vibe code for them are in for a big surprise. This thing might get thru making something simple for them that kinda works but when they try to make a change or fix something this thing is gonna tear their project up so bad they will wish they never heard the word Cursor. Cursor MIGHT get $20 out of them but that will be about it for that! Vibe coders that don’t even know when this thing is going rouge are gonna be smashing their screens LOL, Literally - this thing is a joke!
I completely agree with the Cursor 0.45 LTS idea! 
I agree that situation is so severe, that calling 0,46-47 path finding versions and restarting at 0.45 might accelerate things even if it might not feel that way from cursor perspective.
It would feel a lot of all-nighters went down the drain. But that’s progress I guess.
I am with cursor for almost a year now.
I would say I am an example of ideal beneficiary of vibe-coding. I had some decent basics in coding 18 months ago, 10years as senior data analyst. After learning with AI for 18 months I can do now “full-stack development” using AI delivering paid projects to clients.
I was flying with my project, then something broke like 14 days ago or so. I was not sure what it is. Now back on 0.45 (only changed claud 3.5 → o3mini), things go well again.
Hey Team Cursor, what’s your take on this? Lots of folks are curious. I’ve personally tried out the new version whenever there’s an update, using it for a day, but it hasn’t won me over. Still sticking with 0.45
Just updated to the latest Cursor version. Started a task in manual mode, but the apply code button isn’t showing. Tried creating a custom mode with only MCP selected, but Cursor isn’t calling MCP. Had to revert back to 0.45.17. What’s Cursor up to? Seriously forcing things.
Cursor 0.46+ is unusable for me and others until they allow chat in the left sidebar again (posted about it here). Until that’s possible, no way am I upgrading past 0.45.17.
I don’t want half my screen real-estate to be eaten up by the chat. unnecessarily, I want it to be in my left sidebar with search, files, git control, etc.
Hey, I understand your frustration and desire to have this functionality back. When I’m on my laptop, I also experience discomfort. I’ve already notified the team about this issue, and I hope for a fix.