claude-code - 💡(How to fix) Fix [Bug] Notification hooks not firing for permission_prompt in VS Code extension [1 comments, 2 participants]

TL;DR

The notification hook permission_prompt may not be firing in the VS Code extension due to differences in how the extension handles asynchronous commands compared to the terminal CLI.

Guidance

• Verify that the async: true setting in ~/.claude/settings.json is correctly parsed and applied in the VS Code extension, as it works in the terminal CLI.
• Check if there are any restrictions or limitations in the VS Code extension that prevent the execution of external commands like afplay with the async: true flag.
• Test if the issue persists when using a different sound file or command in the notification hook to isolate if the problem is specific to afplay or the sound file.
• Consider adding logging or debugging statements in the VS Code extension to see if the permission_prompt hook is being triggered but the command is not being executed as expected.

Example

No code snippet is provided as the issue seems to be related to configuration and environment rather than code.

Notes

The issue might be specific to the interaction between the VS Code extension and the macOS environment, given that the same configuration works in the terminal CLI. Further investigation into how the extension handles asynchronous commands and external processes may be necessary.

Recommendation

Apply workaround: Modify the ~/.claude/settings.json to use a different command or sound file to see if the issue is specific to afplay or the async: true setting, as this can help isolate the problem without requiring changes to the VS Code extension itself.