Where I can see the change log of v0.51? I can see nothing on the website.
not yet available probably during creation
What we know so far about 0.51.0:
Some promised features still not available:
- In-app changelog that was already announced as existing in 0.50, is still absent in 0.51.
Some asked for features still not available:
- VSCode version is still 1.96 from November 2024.
- Auto mode still doesn’t show what model is being used.
- Sonnet 4 still doesn’t work with slow requests.
Refreshed look for chat and Cursor settings, including:
In chat window, link to add new models in models dropdown
In settings, card-like look for related settings
Link to docs
The options for YOLO mode are now hidden when turned off, which makes new users feel they shouldn’t turn it on if there are no safety tools available.
A new Memories thing, working only with privacy mode off.
FIXED in 0.51.1: Unlike Background Agents (which show a modal about it instead), Memories don’t show description of what this feature even is about until you turn privacy mode off, which is not only inconsistent, but also quite absurd.
Mentioned above, Background Agents
Open Settings view, no idea what’s loading but it’s taking its sweet time
Also, first time I turned it OFF, it showed a modal with a confirmation that I want to enable it (!). It doesn’t show the second time, so no screenshot.
The modal with information that it requires privacy mode off, also didn’t show the second time, which makes the actual behavior unclear.
Tooltips with basic info about model in Models tab, but for whatever reason - only for Gemini 2.5 pro and Sonnet 4
6 Likes
I saw three changes.
- Updated the layout of the configuration.
- Added a memory feature, which requires turning off privacy mode.
- Background agent feature (I don’t know if everyone has it after the update; I saw in the documentation that it is being gradually rolled out to users), requires turning off privacy mode.
You can now experience the background agent mode of cursor 0.51:
- Must be hosted on GitHub, it can be in private mode, but you need to authorize access to this repository.
- Must turn off privacy mode, after all, it needs access to your repository.
- Must use the max model.
A remote cloud development container will be started. You can work inside it, and once done, a branch will be submitted.
4 Likes
Thank you so much for the details 
1 Like
Hate this UI hiding stuff (“see all models”) - so many pointless clicks and unnecessary confusion..
1 Like
We are still finalizing what the next update will look like once it is GA, so a changelog will be made available once we know everything that will make it in!
Also, expect a new video with a rundown of what’s new!
5 Likes
Is in 0.51.1 the issue with disappearing Cursor Rules fixed?
1 Like
I don’t use Cursor Rules, only Project Rules, so can’t confirm.
What I can confirm is that 0.51 is STILL based on half a year old VSCode 1.96
1 Like
New WSL extension from Anysphere (Cursor Team) recommendation seems to be new.
Maybe also a new auto chat summarization (I haven’t seen it before at least)
2 Likes
Can’t you have a changelog with what you know are already shipped in the code for beta users to check out? For me that would be a big improvement.
3 Likes
Hi, where download v0.51 curosr?
Hey, this version is currently in beta, but you can try to get it right now by enabling early access in Cursor’s settings.
It’s understandable not to want to make a splashy announcement about non-finalized features, but how are users supposed to test fixes/new features with no information? 
An easy solution is a separate changelog URL for pre-releases.
e.g.
Full detailed changelog (including pre-releases):
www.landoleet.org/whatsnew.txt
Release version changelog:
www.reaper.fm/download.php#whatsnew
Or showing it in an editor window after updating.
Having a dedicated forum area for early releases is also worth considering…
5 Likes
I also agree, a separate EAP Category with some changes listed would be great for discussion and feedback.
Once features are shown in UI its not secret anymore
2 Likes
Glad to see they added their own WSL2 extension, installing it now. I see this in the description of the extension:
- Executing all commands, extensions, and terminal operations in Linux
If this statement is true then that is great! Currently I burn through extra tool calls because the agent will almost always try the command in powershell first(the default shell since I’m running in WSL) and will then retry with bash -c <command> even though I have rules explaining that it needs to use Bash. This has always puzzled me because if I open a terminal in Cursor it will be a Bash terminal, but for some reason when the agent uses the terminal it is powershell.
2 Likes
51.2 still no changelog 
2 Likes
A lot of the value of Early Access programs like this is not to actually test the new features, as they will have got the most love internally, but to ensure that the stability, error rate and crashes has not taken a hit.
We want to make sure existing features have no broken in the new update, hence a full changelog is not available for Early Access.
We may work on this in the future, but we can have a lot of hot fixes and changes between the first and last versions of a release!
1 Like
You can find the links for the early access releases here: