Cursor completion sound

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I always lose my completion sound and sometimes system notifications after a cursor update.
Here is my checklist already:
Check - uncheck in settings system notification and completion sound checkbox.
check - uncheck in Win → Notificitation and sounds → Don’t disturb (leaving it Off) and the checkbox for the Cursor app.
And the most important:
Somewhy I need to ctrl + shift + P → and select smth related to ‘composer’ . Previously, it was just ‘Refresh background composer’. But in Cursor 2.0 I must use:
“Open composer as Pane”.
And probably I need to open a fresh tab.
What is going on here?? Why does this bug happen forever?

Steps to Reproduce

See my above checklist

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.34 (user setup)
VSCode Version: 1.99.3
Commit: 45fd70f3fe72037444ba35c9e51ce86a1977ac10
Date: 2025-10-29T06:51:29.202Z
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.22621

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like
2

Hey, thanks for the report. I can see this issue has persisted across multiple updates.

It looks like the sound/notification system isn’t initializing properly after updates despite previous workarounds. The fact that you need to run Composer commands to “wake up” notifications points to an initialization bug.

I’ll pass this to the team. For now, your workaround (Ctrl+Shift+P → “Open Composer as Pane” in Cursor 2.0) is the best option.

Could you confirm:

  • Does it happen after every Cursor update, or intermittently?
  • Does it occur immediately after the update, or only after a restart?

This will help the team reproduce it. Thanks.

3

Hello! nice to hear.

  1. intermittently . I noticed that in some update, there were no bugs at all, and I thought it was fixed. However, after some of the other updates (I’m using cursor since mid June), it occurs every time the computer starts.
    I’m sure 80% in this.
  2. I’m not sure, usually I update the cursor at the start without checking sounds. Maybe yes, but I’m not sure (20%). will tell later about this, will try to check this.
4

Right now for example after the other update (today) I checked everything one by one, calmly checking every time the completion sound.

But the sound started only when I switched (not minimized, but selected) not just the other window like chrome or others like total commander, but I switched to other Tab in the same Agent AI Pane, so I used one to start temporary request, then during request I switched to other Tab in AI pane. And after that I heard that sound. Hope it helps.
(Not even ctrl + shift + P helped today, just switching toggles in settings for completion sound, and during AI response switching tabs (not creating, but switching to previous))

5

Also maybe it’s somehow related to the issue that after EVERY cursor update I need to refresh interface zoom (ctrl + ‘+’) once. EVERY update, maybe some users settings are overrided

6

Thanks for the detailed update. The tab-switch trigger is very helpful context.

The zoom level reset you mentioned is especially interesting. It suggests settings aren’t fully persisted across updates. Could you check if any other settings reset as well (e.g., theme, hotkeys, or other preferences)?

I’ll track your timing answers and pass them to the team. The initialization pattern is clear now.

1 Like
7

I don’t use other settings like theme-hotkeys.
But I always open 2 cursor applications (like 2 windows), one for the documents project, and one for the project with the code at the same time. And when I click the button to start to update, usually both are open

8

Thanks for the info, that’s very helpful.

1 Like