[FEATURE] Add Inactivity-Based Notification Delay for Claude Code Alerts

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude Code currently sends system notifications (via iMessage or other native notification
systems) immediately when it needs user attention, permissions, or approval. This creates
notification fatigue when users are actively engaged with the application, as they receive
redundant alerts while already looking at and interacting with the Claude Code interface. The
immediate notifications are disruptive to workflow and unnecessary when the user is present and
engaged.

Proposed Solution

Implement an intelligent notification delay system that monitors user activity and only sends
system notifications after a configurable period of inactivity (default: 30 seconds). The system
would:

1. Track user interactions - Monitor when the user last interacted with Claude Code (typing,

clicking, scrolling, etc.)

1. Queue notifications - When Claude needs attention, queue the notification instead of sending

immediately

1. Smart delivery - Only send the queued notification if the user hasn't interacted within the

timeout period

1. Immediate clearance - Clear pending notifications if the user interacts before the timeout
2. Configurable timeout - Allow users to set their preferred inactivity threshold (e.g., 1, 5,

10 minutes, or disabled)

This would significantly improve the user experience by reducing unnecessary notifications while
ensuring important alerts still reach users when they're actually away from the application.

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_