Cursor v1.5 - Pre-release Discussions

However, even in the worst companies, testers are informed about what has been changed. Only in Сursor we have to figure it out ourselves…

7 Likes

After updating to version 1.5, I noticed Notepad is gone! Did you remove Notepad? Now I can create a new Notepad via command, but what about the Notepads I already created?

I’ve had this for a week already!
And this terrible problem still isn’t getting fixed.

Thank you — glad to hear it.
What do you mean by
“notifications are now available”?
Is that something that wasn’t there before?
Can you explain in more detail?

Previously, we provided an audio notification when the Agent completed a run. From now on, you will also receive desktop notifications. This will happen when the Agent requires your input (such as confirming an Auto-run choice) and when it finishes a run.

This improvement ensures that important stages of Agent are not missed: audio notifications can be inaudible if you’re playing music or have hearing impairments, whereas desktop notifications are always visible on your screen.

You can set your preference in Settings > Chat.

8 Likes

This is really good — I’ve been waiting for this for a long time.

I’ve been on this version for over a week, and I’ve never received such notifications.
I also can’t find it in the settings — can you explain in detail?

We have just today released 1.5.0, could you check your version?
If you do not have yet 1.5.0, its in Early Access and we are ramping up rollout.

image
I found it, but it has never actually sent me a notification.
Maybe it just hasn’t happened enough for it to need me, since I’m in a mode that lets the agent do everything.
I thought this was meant to solve the problem of the terminal getting stuck forever for no reason but that wasn’t the intention.

I’ve had this for over a week — isn’t that what it is?
Oh, I see — I’m not even on that at all.

Version: 1.4.5 (user setup)
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

There is under that option a new one in 1.5.0

1 Like

And can I hope that the scrolling issue has been fixed too?
That would make me really happy.

I’m not sure about that. May have to check which issue you refer to! :sweat_smile:
Sent you a DM to connect with my colleague on this.

1 Like

Can you guys work on your changelogs? They are very, very sparse, and do not cover in detail everything that was fixed, updated, added, improved, etc. with each release. That makes it hard to tell which version might have introduced something…well either great, or a new bug that is causing you problems.

Additionally, it would be nice to have a built-in downgrade feature so you could roll back to a previously known-working version of Cursor, when a new release introduces something that greatly hampers your workflow.

Regardless though, you guys need much more detailed change logs that explain EVERYTHING in each release. Your existing change logs seem extremely sparse and lacking in detail.

9 Likes

This. I don’t understand why they don’t share a changelog with beta users, so we know what to test.

We get that, it’s a beta and all, but you can have a beta changelog that is subject to updates as the beta progresses.

Then when the beta over, promote the changelog to release changelog, boom you’re ahead of the game :tada:

8 Likes

Hey, thanks for the feedback, I completely agree with you, I’ll pass this on to the dev team.

4 Likes

Well this is embarrassing. The issue I was reporting I can now recreate in VSCode. Tracked it down to a recent update of the GraphQL: Language Feature Support extension. Ignore me.

4 Likes

I have had this problem. It seems to occur when I’ve had the IDE running for a long time. I’ve found that usually (not always) closing it and reopening resolved the issue an I am able to CMD+Click my way through again.

As to why it occurs in the first place, I don’t know. Hopefully there was a legit fix for a bug.

I think we have a perspective mismatch.

You think you’re a beta tester, validating new features before they go GA.

They think you’re a smoke tester who just uses new releases and alerts them if you find anything broken.

One is an ancillary resource that collaborates with the company to make a better product. The other is a lab rat. :joy:

4 Likes

Ah, the exquisite taste of raw truth! :rofl:

Thank you so much! Detailed change logs will be very welcome! :slight_smile:

1 Like

This worked. Thank you for the tip.