[BUG] Notification hooks not firing for permission_prompt in VS Code extension
Resolved 💬 11 comments Opened May 3, 2026 by Maschina Closed Jun 30, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
The Notification hook does not fire in the VSCode extension version of Claude Code.
Actual Behavior
- Permission dialog is displayed as expected
- However, the Notification hook does not fire
- No log file is created by the hook command
- PreToolUse and Stop hooks work correctly
What Should Happen?
Expected Behavior
According to the documentation (https://code.claude.com/docs/ja/hooks#notification), the Notification hook should fire in the following cases:
- When Claude Code requests permission to use a tool
- When the prompt input has been idle for at least 60 seconds
Error Messages/Logs
None
Steps to Reproduce
- Configure a Notification hook in settings.json with a command that logs to a file
- Reload VSCode window
- Configure permissions.ask to require confirmation for specific tools (e.g., Bash)
- Execute a tool that triggers the permission dialog
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.123
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
- When the permission dialog was displayed, the Notification hook did not execute
- The log file specified in the command was never created
- Other hooks (PreToolUse, Stop) work as expected
- Workaround: Using PreToolUse hook with matcher "Write|Edit|Bash|NotebookEdit" to achieve similar functionality
- Unclear if this issue exists in the CLI version
- This may be specific to the VSCode extension
This issue has 11 comments on GitHub. Read the full discussion on GitHub ↗