Hey,
Cursor has an updating mechanism built in so that, when there is an update, you a prompted as such, and it will install when you next close the application. There should never be any loss of settings or project history when updating through this method.
Currently, there is no way to roll back your version officially. You can find and download olds builds, but there is a high risk of data loss if you do this, as there is no procedure for data migration when downgrading versions.
We have a release plan that aims to iron out any teething issues with new releases before they are released to everyone, including a beta testing program and a distributed rollout schedule. Therefore, by the time you get an update, there should (in an ideal world) be no bugs or issues added by accident.
We do offer new features to our users early in development, so they can try them and give us feedback, so it may be that the newest features still require some maturing before they could be considered “enterprise-ready”, but this is really a decision per user, hence we leave the option to you.
The reason for VSCode as a base is that we don’t want to build an editor. VSCode is the primary editor for engineers worldwide, regardless of the language, framework, or technology people hope to build with it. As such, it was the obvious choice as a base for an editor. We believe we can have much more impact on software development focusing on the new AI features than trying to improve upon the strong foundation VSCode already provides.
Text search through the entire codebase is already available and is brought over from VSCode. More info on that can be found here: Basic editing in Visual Studio Code
I apologize you are having a bad day with Cursor, the best advise I can give is two-fold:
- Routinely restart your Composer sessions, as long sessions can cause the AI to be confused, and forget your old context and messages - even its own changes if they were long enough ago!
- Write documentation for the AI, even short and sweet, can help when starting a new composer, or changing the area of your codebase you are working on. A short
.mdfile explaining the structure of your codebase can really help an AI understanding things better than just writing a prompt for it can. You can write a few of these, and @ them whenever needed, to help the AI stay back on track.
Regarding documentation, you can find it at docs.cursor.com, although we are in the process of reviewing and updating them to be more aligned with the current state of the editor today.