Preflight Checklist

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

Problem Statement

The idle_prompt notification hook currently has a hardcoded 60-second timeout before it triggers. For users who multitask while Claude Code is running, this delay means we often don't realize Claude is waiting for our input until we manually check back much later.

I have ADHD and frequently switch between windows while Claude Code works on tasks. When Claude needs my input, I assume it's still processing and continue with other work. By the time the 60-second notification fires (if I even notice it), I've often completely forgotten I was waiting for Claude Code and have context-switched to something else entirely.

I know this seems minor, but for neurodivergent users who struggle with task-switching and working memory, a shorter configurable timeout (like 30 seconds, or even 15) would significantly reduce the friction of working with Claude Code in a multitasking workflow.

Proposed Solution

Add a configurable idle_prompt_timeout setting in settings.json that allows users to customize when the idle_prompt notification fires.

Example configuration:

{
  "idle_prompt_timeout": 30,
  "hooks": {
    "Notification": [
      {
        "matcher": "idle_prompt",
        "hooks": [
          {
            "type": "command",
            "command": "powershell -Command \"(New-Object Media.SoundPlayer 'path/to/alert.wav').PlaySync()\""
          }
        ]
      }
    ]
  }
}

The timeout value would be in seconds and default to 60 to maintain current behavior.

Alternative Solutions

Related issues #13024 and #13830 request immediate notification hooks for AskUserQuestion and other waiting states. Either of these solutions would also address my use case:

• A new hook that fires immediately when Claude yields control (issue [FEATURE] Add hook for when Claude is waiting for user input #13024)
• Notification support for AskUserQuestion events (issue Feature Request: Add notification hook support for AskUserQuestion events #13830)

However, a configurable timeout for idle_prompt would be simpler to implement and wouldn't require new hook types.

Priority

Medium - Impacts workflow efficiency for users with ADHD and other neurodivergent users who multitask

Feature Category

Configuration and settings

Use Case Example

1. I ask Claude Code to help implement a feature
2. I switch to my browser to research something while Claude works
3. After 30 seconds, Claude is waiting for my input
4. My configured 30-second notification plays an alert sound
5. I switch back to the terminal and respond to Claude's question
6. Work continues with minimal context-switching friction

With the current 60-second timeout, I often don't realize Claude is waiting until I've been doing something else for several minutes, making it much harder to resume the task.

Additional Context

I'm a blind screen reader user with ADHD, so audio notifications are essential for me to know when Claude Code needs attention. The notification hook system is excellent, but the hardcoded 60-second delay is just long enough that I've usually moved on mentally to something else by the time it fires.

Even if the configurable range was limited (e.g., 15-60 seconds) to prevent notification fatigue, it would be a huge quality-of-life improvement for users who need faster feedback about Claude's state.