Old system notifications do not get removed automatically after they are no longer relevant (once I have reacted to the event that caused them). It is annoying to go through a stack of stale notifications and close each one manually.
Hey, thanks for the feature request. Right now, system notifications in Cursor work as fire-and-forget. They stay in the OS tray until you close them manually, and they don’t clear automatically after you’ve responded to the event. So what you’re seeing isn’t a bug, it’s just that this capability isn’t supported yet.
It’s a good idea though. Auto-clearing notifications that are no longer relevant, like when the related chat or event has already been viewed, would help avoid a pile of outdated alerts. I’ve passed this to the team as feedback.
I can’t share a timeline for this feature, but if there’s an update, I’ll reply here. If you notice related cases, like a stuck unread badge, let me know. That’s a separate issue we track.
The issue I’m getting may be related to this, as I often get “unable to save file” notifications from time to time, as soon as I open the project window in (WSL) IDE, even when I don’t have any uncommitted work!
When this happens, Cursor doesn’t process any requests that I send. So have to manually click close without saving for each file. And it may keep doing this a few times in a row.
If I just close the window and reopen it, the issue persists.