claude-code - 💡(How to fix) Fix Built-in sound notification when Claude is waiting for user input [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45014Fetched 2026-04-09 08:15:22
View on GitHub
Comments
2
Participants
3
Timeline
4
Reactions
0
Author
Timeline (top)
commented ×2labeled ×2

Fix Action

Fix / Workaround

Problem with current workaround: The hook-based workaround requires users to grant permission in every new session for the sound command to execute, which defeats the purpose of a seamless notification experience:

RAW_BUFFERClick to expand / collapse

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

Currently there is no built-in audio notification when Claude finishes processing and is waiting for user input. For long-running tasks (wiki updates, code exploration, etc.), users have to keep watching the terminal to know when Claude needs their input — similar to how Slack or Outlook play a notification sound for new messages.

Problem with current workaround: The hook-based workaround requires users to grant permission in every new session for the sound command to execute, which defeats the purpose of a seamless notification experience:

{ "hooks": { "Notification": [{ "hooks": [{ "type": "command", "command": "afplay /System/Library/Sounds/Bottle.aiff &", "timeout": 5 }] }] } }

Proposed Solution

Add a first-class setting like notificationSoundEnabled: true/false and optionally notificationSoundFile: "path/to/sound" Play a system sound without requiring any permission prompt — just like Slack/Outlook notifications Support platform-specific defaults: macOS (afplay), Linux (paplay), Windows (powershell [System.Media.SystemSounds]) This should work out of the box without hooks or permission approvals each session

Alternative Solutions

No response

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

Engineers frequently multitask while Claude processes long operations (code exploration, wiki updates, PR reviews). A simple notification sound — same as Slack/Outlook — would let them switch to other work and come back when Claude needs input.

Additional Context

No response

extent analysis

TL;DR

Implement a built-in audio notification feature with a configurable setting, such as notificationSoundEnabled, to play a system sound when Claude finishes processing and is waiting for user input.

Guidance

  • Introduce a new setting, notificationSoundEnabled, to enable or disable the audio notification feature.
  • Add an optional notificationSoundFile setting to allow users to specify a custom sound file.
  • Use platform-specific commands to play the system sound, such as afplay on macOS, paplay on Linux, and powershell [System.Media.SystemSounds] on Windows.
  • Ensure the notification sound plays without requiring permission prompts, similar to how Slack and Outlook notifications work.

Example

{
  "settings": {
    "notificationSoundEnabled": true,
    "notificationSoundFile": "/System/Library/Sounds/Bottle.aiff"
  }
}

Notes

The implementation should consider platform-specific differences and ensure a seamless notification experience without requiring user permission for each session.

Recommendation

Apply a workaround by introducing a configurable audio notification setting, as this feature is not currently available and has a high priority impact on productivity.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING