LTS version proposal

[normalnormie (Norman)]

We need a stable LTS version that our community has thoroughly tested and approved. This should be the default recommendation instead of newer beta versions that often disappoint new users.

Thankfully, the Cursor team listens to our feedback, allowing us to disable updates. Let’s discuss and vote on creating an LTS version, as two topics already address this.

Personally, I’d prefer an LTS based on version 0.45.14 with minimal necessary fixes (like the mcp global attribute in the UI). This would help developers clearly distinguish between production-ready versions and experimental versions with new features.

It's remarkable how Cursor Chat 0.45 + 3.7 can't be beat

I’ve been using 0.45.17 and it’s just so good. I don’t know why. Is it the prompts? Maybe it sticks more to the letter of the law due to smaller context window so attention on the requested task is stronger? I’ve tried 0.46 and most recently 0.47, with MAX. I was able to quickly bang out a very complex session management improvement to our Next.js codebase with 0.45 that I could not get 0.47 to do after a much longer conversation and far more elaborate attempts. I got a very satisfactory res…

Cursor 0.45 LTS

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.

[UnknownEntity (UE)]

This should be Cursor’s TOP Priority… if not Cursor could end up like ownCloud… or Oracle’s OpenOffice was bug ridden LibraOffice forked off so the product could be better… which now you are seeing alot of Big Dogs coming out with their own IDE with Coding Agents..

Where is the suggestion box for the Product Officer? If the C-Suite is not being advise on the amount of legitimate concerns from the Cursor community - C2 has completely broken down and well… we all know what happens after that….

[hlspablo (Pablo Henrique)]

@normalnormie where we disable the updates? I searched everywhere in settings, but I don’t find

[Serp]

It sounds nice, but I think it will run to real world problem: dependency of external API’s with models.

The code probably needs to be updated from time to time to fully support those models.

[hlspablo (Pablo Henrique)]

I don’t think so…, we have pretty old versions working, all the logic is done server side, not on IDE

[Serp]

You are just lucky. There are markup codes for syntax coloring and who knows what else. But I suppose it is possible to maintain the old version compatibility on the server too.

[HunterMontgomery]

This would be great for enterprise customers. I’ve had cursor uninstall itself on an update, ripgrep not being installed causing most ai searches to fail, terminal output not being routed to the ai, the wrong worktree being used after an update, apply all not applying any changes to the file, and weird behavior when closing tabs from multiple models with unsaved changes.

Every update feels like a gamble between having your bugs be fixed and breaking even more. I enjoy gambling, but I have work to do.