Not getting notifications for sub-agents Allow/Deny request

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

At my work, we cannot auto-allow all requests in Cursor as we have to monitor any new commands that Cursor is executing.
And because of that, I heavily rely on notifications. When I get it, I review it and I allow it accordingly.

However, since Sub-Agents were introduced, Sub-Agents sometimes require permissions to be approved manually.
Unfortunately, due to a Cursor bug, when Sub-Agents create those allow/deny requests, they do not show up as notifications. Hence, the agents are stuck at that point indefinitely until I open Cursor and approve it. Which is a very manual and tedious process

Fix: when subagents generate the allow/stop request, they should show up in notifications as well, just like the main agent.

Steps to Reproduce

  1. Make sure your run mode is Allowlist.
  2. How zero or very few commands in Allowlist
  3. Create a request that would be very heavy and would essentially trigger sub-agents. (Example: run and fix multiple tests in parallel.)
  4. Make sure that cursor is not focused so that you will get a notification.
  5. Wait for the agent to create sub-agents - and wait for it to ask for permissions.
  6. You will realize only the main agent is able to create those notifications, however, not the sub-agent.

Expected Behavior

Sub-Agent should create the notifications as well.

Operating System

MacOS

Version Information

Version: 3.12.17 (Universal)
VS Code Extension API: 1.128.0
Commit: 0fb762053c34788bb7760d5673f8a6d4c8589d50
Date: 2026-07-17T02:53:53.006Z
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: Darwin arm64 25.5.0

For AI issues: which model did you use?

Cursor Grok 4.5 High

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey thanks for the detailed report. This exact bug with sub-agents (they were not sending system notifications when requesting allow/deny although the main agent was sending) was fixed and the fix is already in your version 3.12.17. So on the current build the sub-agent should send a notification with Accept/Reject buttons and it routes to the parent agent.

It looks like you are describing the behavior since Sub-Agents were introduced. There is a chance that after updating to 3.12.17 you have not rechecked yet. Can you run your repro again specifically on 3.12.17 and clarify a couple of things:

  1. Does it still reproduce after updating to 3.12.17?
  2. When you return to Cursor is the Allow-prompt on the parent agent in place or has it disappeared completely? If the prompt disappears this is already a different issue (prompt loss) and the approach to it is different.
  3. Are System Notifications enabled in Settings? (judging by the fact that the main agent sends notifications yes but just in case.)

If on 3.12.17 it still reproduces with a visible prompt let me know and we will report it as a regression. Write how it goes.