VS Code extension: Notification hooks not firing and no native VS Code notifications
Resolved 💬 3 comments Opened Feb 19, 2026 by umutakin-dev Closed Feb 23, 2026
Description
When using Claude Code through the VS Code extension, the Notification hook configured in ~/.claude/settings.json never fires. Additionally, the extension does not register as a VS Code notification source, so no native VS Code notifications are shown either.
The same hook works correctly when using Claude Code from the CLI.
Steps to Reproduce
- Configure a Notification hook in
~/.claude/settings.json:
{
"hooks": {
"Notification": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "osascript -e 'display notification \"Claude needs attention\" with title \"Claude Code\" sound name \"default\"'"
}
]
}
]
}
}
- Use Claude Code from the CLI (
claudecommand) — notification fires correctly - Use Claude Code from the VS Code extension — no notification at all
Additional Context
- The extension does not appear in VS Code's notification sources list (Settings > Notifications > Select sources), confirming it doesn't register as a notification provider
- Running the hook command manually via Bash from the extension context works fine — the issue is that the
Notificationevent is never emitted - macOS Sequoia, VS Code latest
Expected Behavior
- The
Notificationhook should fire from the VS Code extension just as it does from the CLI - Ideally, the extension should also register as a VS Code notification source for native IDE notifications
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗