[BUG] Notifications should not fire in auto-accept/yolo mode sessions
Problem
When running Claude Code in auto-accept mode (e.g., --dangerously-skip-permissions or yolo/auto-accept edit mode), system notifications still pop up on Windows, interrupting the user's other work for no reason.
Since these sessions auto-accept everything, there is nothing for the user to act on — the notifications are pure noise and disruptive.
Steps to Reproduce
- Start a Claude Code session in auto-accept/yolo mode
- Let it run a multi-step task
- Observe Windows notification popups appearing throughout, even though no manual approval is needed
Expected Behavior
Sessions running in auto-accept mode should suppress all notification popups (especially permission_prompt and idle_prompt types), since the user has explicitly opted out of manual approval.
Notifications should only fire in sessions where user action is actually required.
Current Behavior
Notifications fire regardless of the session's permission mode, causing constant interruptions when the user is focused on other work.
Environment
- Windows 11
- Claude Code CLI (terminal)
Suggested Fix
The Notification hook should be aware of the session's permission mode. If the session is in auto-accept/yolo mode, suppress permission_prompt and idle_prompt notifications by default. Alternatively, add a notification type filter or session-mode-aware setting in settings.json.
Related Issues
- #22702 — Allow suppressing background task notifications via Notification hook
- #12046 — Option to disable notifications
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗