Feature request: Sound notification for permission prompts in VSCode panel

[OENice]

Feature Request

When using Claude Code in the VSCode panel, permission prompts (tool approvals, questions, etc.) appear silently inline. There is no audio notification to alert the user that Claude is waiting for input.

Problem

When working across multiple windows or stepping away briefly, it's easy to miss that Claude Code is waiting for approval. VSCode's built-in accessibility.signals.notification* settings do not apply because Claude Code renders prompts inside the panel rather than using VSCode's notification API.

Proposed Solution

Add a sound/audio alert when Claude Code requires user interaction (permission prompts, questions). This could be:

1. A built-in setting in the Claude Code extension (e.g., claudeCode.notificationSound: true)
2. Integration with VSCode's accessibility signals so existing settings work
3. Using VSCode's standard notification API alongside the inline panel prompt

Environment

• VSCode on Windows 11
• Claude Code extension v2.1.109
• Panel mode

[PettHa]

Same use case (VSCode panel on Windows). Until a built-in setting lands, the workaround is to use the Notification hook plus a PreToolUse matcher for AskUserQuestion and ExitPlanMode (the AskUserQuestion case doesn't fire the native Notification event, see #44326).

I wrapped this in a plugin so the setup is one install command rather than every user assembling it themselves. Uses Windows System.Speech for the audio, plus a colored frame pulse around the primary monitor so the alert is visible even if VSCode is in the background.

Repo: https://github.com/PettHa/tts-attention-alert

[stephenpiscura]

Similarly, here’s the prompt Claude generated during a session in VSCode for Mac:

Summary

When Claude Code pauses to request permission for a tool use, there is currently no way to receive an OS-level notification. Users who switch to another window while Claude is working can miss approval prompts for minutes at a time, stalling the session without any signal.

Current behavior

The only available hook, PreToolUse, fires before Claude Code decides whether to ask for approval — so it triggers on every tool use, including auto-approved ones. There is no way to distinguish "this will require approval" from "this will run automatically" from within the hook. A notification based on PreToolUse therefore creates noise on every command and doesn't accurately signal when action is required.

Requested behavior

One or both of the following:

1. A dedicated hook event — e.g. PermissionRequired or AwaitingApproval — that fires only when Claude Code actually pauses and waits for the user to approve or deny a tool use. This would allow users to trigger OS notifications, sounds, or other scripts precisely when their attention is needed.
2. A built-in notification setting — a simple "notifications": true option in settings.json that sends a native OS notification whenever Claude Code is waiting for approval.

Use case

Many users work in a flow where Claude runs independently for several steps while they switch to other tasks. The session silently stalls at an approval prompt, and the user has no way to know without periodically checking the terminal.

Workaround attempted

PreToolUse hook → osascript macOS notification. Removed because it fires indiscriminately and doesn't match the actual approval moments.

Environment

• macOS Sequoia 26 (Beta)
• Claude Code CLI v2.1.141
• Terminal mode (zsh)

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.