Linux tray / unread list does not show which editor window is waiting on Allow (lists archived chats; omits the focused one)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I run several editor windows at once, one per repo, so I can see what each agent is changing. When an agent needs Allow (shell, web search, etc.), I get a desktop notification that doesn’t tell me which window. I click through four or five windows until I find the prompt.

Clicking the top-bar icon (the Linux tray) is worse than useless. I get a semi-random list of agent chats. They do tend to be on the recent side but many have been closed and dormant for a while. Some have black dots. This also appears to be random and has no correlation with chats with unseen agent info or which are waiting for approval. The chat that is actually waiting on approval often does not appear in the list at all. (The icon/tray notifications have always been unhelpful and I just ignore them, but I figure I’d mention them since they’re an obvious way to attempt to answer my “which window is asking for permission?” question, so I wanted to explain why that doesn’t help.)

This is not the Glass UI session-bar bug where a subagent keeps the “working” dots inside one window. I am in several editor windows. I use those windows to watch diffs; I am not going to put all of that in one Agents Window.

Steps to Reproduce

  1. On Ubuntu, open several Cursor editor windows, each on a different folder/repo. Run an agent in more than one of them.

  2. Leave Auto-run such that some tools still prompt (e.g. web search, network, or a command not on the allowlist).

  3. When a prompt appears, note: OS notification + (sometimes) red dot on the top-bar Cursor icon. Neither names the window or workspace.

  4. Click the top-bar icon. Note which chats are listed, which have dots, and whether clicking them opens a pending Allow.

  5. Confirm a closed/archived chat can still have a dot, and that the focused window that is waiting on Allow may be missing from the list.

Expected Behavior

  • Notification and tray should name the workspace / window / chat, not only “Cursor wants something.”

  • Clicking either should focus the window that is blocked on Allow.

  • The tray list as a whole, or the dots feature of the try list, should only include chats that still need attention. Archived or closed chats should not have a dot. The chat that is waiting should be listed even if that window is focused.

  • A dot should mean a pending Allow, or some other state that is labeled as such.

Operating System

Linux

Version Information

Version: 3.12.17
VS Code Extension API: 1.128.0
Commit: 0fb762053c34788bb7760d5673f8a6d4c8589d50
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Linux x64 6.8.0-136-generic

Does this stop you from using Cursor

No - Cursor works, but with this issue

10

Hey @Shauna_GM, thanks for the detailed report! We’ve shared all this feedback with the team.

One thing that should help in the meantime: clicking the desktop notification itself is meant to focus the exact window that is waiting. If that isn’t working on your setup, could you let us know which Ubuntu desktop environment you’re using (GNOME, KDE, etc.)? That would be a useful data point.