Claude Code notifications in VS Code and JetBrains

Updated

Quick answer

The terminals inside VS Code, Cursor and JetBrains IDEs show nothing when Claude Code finishes: they do not display the notifications that iTerm2 or Ghostty do. Hooks still run there, so a Stop hook gives you an alert. In the VS Code extension’s own panel, permission prompts have at times not fired the Notification hook, so PermissionRequest is the one to rely on.

Why IDE terminals stay silent

Claude Code has its own notifications, chosen by the preferredNotifChannel setting. With the default value, "auto", it sends a desktop notification only when it detects iTerm2, Ghostty or Kitty, rings the bell in Apple’s Terminal when its audible bell is off, and does nothing anywhere else. The integrated terminals of VS Code, Cursor and the JetBrains IDEs fall in “anywhere else”: Claude finishes, and nothing happens until you look.

Two settings change that without a script. "terminal_bell" makes Claude Code ring the bell character in any terminal; whether you hear it then depends on the IDE’s own terminal bell setting, which is often off. And hooks, which Claude Code runs itself, work in every terminal.

A hook that works in any IDE terminal

A hook is a command Claude Code runs at a fixed point. Stop runs each time Claude finishes responding; Notification runs when Claude waits for you. Both live in ~/.claude/settings.json, the file the command line and the VS Code extension share, so one configuration covers the integrated terminal, an external terminal and the extension.

macOS, in ~/.claude/settings.json

{
  "hooks": {
    "Stop": [
      { "hooks": [{ "type": "command",
        "command": "osascript -e 'display notification \"Claude finished\" with title \"Claude Code\"'" }] }
    ],
    "Notification": [
      { "matcher": "permission_prompt|elicitation_dialog",
        "hooks": [{ "type": "command",
          "command": "osascript -e 'display notification \"Claude needs you\" with title \"Claude Code\"'" }] }
    ]
  }
}

On Linux, replace the command with notify-send 'Claude Code' 'Claude finished'. On Windows, Anthropic’s hooks guide gives a PowerShell line that opens a message box, which can open behind the IDE window. On macOS, osascript shows its notifications as Script Editor: if nothing appears, allow notifications for Script Editor in System Settings › Notifications, since macOS never asks.

Check the result with /hooks in the terminal. In the VS Code extension, the Customize section lists the hooks loaded in the session, grouped by event, from Claude Code v2.1.269.

The VS Code extension panel

The extension’s chat panel is a different host. Claude Code sends its permission requests to the panel through the Agent SDK, the same way the Claude desktop app does, and that changes when the Notification hook fires for a permission:

PermissionRequest is steadier. It runs the moment Claude Code is about to ask, and for a request that goes to the panel, the hook runs alongside it: whichever decides first applies. A hook that only alerts you and prints nothing leaves the decision to the panel. If you use the panel and want an alert you can count on, put it there.

An alert the moment Claude asks, in ~/.claude/settings.json

{
  "hooks": {
    "PermissionRequest": [
      { "hooks": [{ "type": "command",
        "command": "osascript -e 'display notification \"Permission needed\" with title \"Claude Code\"'" }] }
    ]
  }
}

JetBrains

The JetBrains plugin doesn’t bundle Claude Code: it runs the claude command in the IDE’s integrated terminal and connects to it. Everything above applies as in any terminal. The notifications the plugin’s settings mention are about setup, such as the one shown when claude isn’t on your PATH. For Claude finishing or waiting, use the Stop and Notification hooks, or run claude in iTerm2, Ghostty or Kitty and connect it to the IDE with /ide, which brings back the built-in notifications.

When you leave the IDE

A desktop alert waits on the screen of the computer you walked away from. To get it on your iPhone and answer it there, pair Monish from the IDE’s integrated terminal:

In the IDE’s terminal, with the 6-digit code from the app

curl -fsSL https://monish.cc/install.sh | sh -s 482913

The command adds Claude Code hooks to ~/.claude/settings.json, so they apply to every session that reads that file. A permission request reaches your lock screen with the exact command and Allow and Deny; a question arrives with its options; a finished turn comes with Claude’s last line, and a reply becomes its next instruction. Monish is free and needs no account. The hooks you added above can stay.

If you have a Claude plan, the extension can also connect a session to Remote Control with /remote-control in its prompt box. The Claude app then pushes permission prompts and questions for that session, once you turn on Push when actions required in /config; it needs a claude.ai sign-in rather than an API key.

Questions

Why does Claude Code notify me in iTerm2 but not in VS Code?
Claude Code sends its own desktop notifications only when it detects iTerm2, Ghostty or Kitty. In other terminals, including the ones in VS Code and JetBrains IDEs, it does nothing unless you set terminal_bell or add a hook.
Do hooks run in the VS Code extension?
Yes. The extension and the command line share ~/.claude/settings.json, hooks included, and the extension’s Customize section lists the hooks loaded in the session.
Which hook should I use for permission prompts in the extension panel?
PermissionRequest. It runs as soon as Claude Code asks. In the panel, the Notification hook fires about six seconds later on recent versions, and did not fire at all before v2.1.233.
Does this work in Cursor?
Yes. Cursor’s integrated terminal behaves like VS Code’s: Claude Code shows no notification there by itself, and hooks run as usual.

More guides

New to Monish? The home page shows what lands on your iPhone, and all guides are listed here.

Get Monish on your iPhone

Free, no account. Your 6-digit code is waiting in the app.

Download on the App Store