As some have you may have spotted, v0.46 is on its way, with some spruced-up UI and some agent improvements
We are currently in the process of getting v0.46 ready for it’s full release, and we are slowly rolling it out to a select batch of users to ensure nothing is seriously broken and we ruin everyone’s day!
Once available, all users will get the update automatically, downloading from cursor.com will not get you the update early!
As always, the full changelog will be available here, once v0.46 is widely available:
Feel free to discuss here, this thread will be converted to the release discussions once it’s out fully
We’ve got plenty of cool stuff in the works behind the scenes, but we hope this release helps you bit even more productive, and love using Cursor even more!
Really impressed so far, love the unified Ask → Agent
Can’t wait to read the release notes with all the great stuff.
The normal flow with most products is:
Hype up the new features on social media
Announce the new release (changelog)
Release the new version
I had been using 0.45 for a week before the release notes came out and the release notes lack so much context. A full blog release with screenshots and context (Why you did x) would be idea. I would love to know more.
Can you please provide a specific documentation about set up for “npx” command in windows OS, because some of the users are can’t setup properly the npx command.
I think the MCP changes are all good, I might like even more to help debug things, though. For example, I know I can see some information in VS Code’s Output tab with “Cursor MCP” selected in the dropdown, but when my MCP server isn’t starting correctly I see limited information and changing the log level to debug or trace isn’t increasing verbosity.
Sorry to report: The new version of cursor has been really buggy for me folks. It’s crashed maybe, 6 times, in the last hour?
When it has crashed, it has done a poor job of “restoring” state. In one instance, I had gone down a conversation tree with cursor, backed out of it because it had incorrectly implemented functionality. After that, I decided to build it myself. I Built it, ran my build, liked what I did, then, it then crashed, and restored it to the pre-revert state / old conversation included.
This most immediate crashing problem is really important to me (happy to provide logs, I see "Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
at s.send (node:electron/js2c/browser_init:2:91810)
at _.send (node:electron/js2c/browser_init:2:75243)
at Ay.send (file:///tmp/.mount_cursorDlF8o3/usr/share/cursor/resources/app/out/main.js:36:23295)
at Ip.p (file:///tmp/.mount_cursorDlF8o3/usr/share/cursor/resources/app/out/main.js:34:19056)
at Ip.o (file:///tmp/.mount_cursorDlF8o3/usr/share/cursor/resources/app/out/main.js:34:19021)
" spammed in my console out, however, avoiding accidentally deleting the user’s code by confirming when about to apply a revert that is meaningfully different than what is on disk is extremely important.
FWIW, even in older versions of cursor, the revert behavior had specific quirks to it (around how you had to “accept all” before hitting the revert button when doing chat operations, etc), that I’d learned to work around, but I’ve always felt that you needed more reliable code history management if you’re going to allow chat state to meaningfully revert code in my repo in such a way upon a crash.
It was a little confusing to me that the new UI changes combined chat and composer. I thought Copiliot was taking over or something, as now I see 2 chat buttons in the sidebar (even though I don’t even have the copilot extension installed). Was able to hide the copilot chat though!
I appreciate breaking out the settings into more menu’s to find things easier. I would love the Docs to be split out as well for clearer management, as I use them heavily and have quite a few.
Looking forward to trying the new/updated features!
Good update guys! Making chat and agent in one menu mostly good solution. But for me it was a bit more comfortable to split them so i can find information faster
Yesss. Changelogs definitely need more love. I really enjoy how [redacted] does it, nice graphics, Twitter post, etc. It makes it more exciting to upgrade.
I’m facing error in agent mode in v0.46, instead of auto fixing files like it was in v0.45.11, it just shows suggestion and code. I remember there was a thread talk about this.
