Claude Code notifications not working: five causes

Updated

Quick answer

When a Claude Code notification never shows, the cause is almost always one of five: the hook is not loaded, the JSON in settings.json is invalid, the command fails silently, the event you chose does not fire in your setup, or the system is hiding the alert. Run /hooks, then claude --debug, and test the command by hand.

Is the hook loaded

Type /hooks at the Claude Code prompt. It lists every hook the session loaded, grouped by event. If yours is missing, the problem is in the file, not in the command:

Does it run

A listed hook may still fail every time without telling you. A failed hook on an event such as Notification shows no error in the transcript at all. Ask for the details:

Start Claude Code with a debug log you can follow

claude --debug-file /tmp/claude.log
# in another terminal
tail -f /tmp/claude.log

Trigger the event, then look for your hook in the log. If you started without the flag, /debug turns logging on mid-session and tells you where the log is. Press Ctrl+O for the transcript view, where a hook that failed on most other events shows a hook error notice with its exit status.

Does the command work by hand

Most broken hooks are broken scripts. Feed yours the kind of JSON Claude Code sends and watch what happens:

Run the hook yourself

echo '{"hook_event_name":"Notification","notification_type":"permission_prompt","message":"test","cwd":"'"$PWD"'"}' \
  | ~/.claude/hooks/notify.sh
echo $?

Is it the right event

A hook can be loaded and correct, and still wait for an event that doesn’t come when you expect it.

Is the system hiding it

The hook ran and the command succeeded, but nothing appeared. The operating system decided that.

With Monish: monish status

If you use Monish, start with two commands on the computer:

On the computer where Claude Code runs

monish status
monish test

The first checks the setup on that computer. The second tests the whole path: it sends a test request to your iPhone and prints what you answered, or that no answer came. If something is off, run the install command again with a new 6-digit code from the app. Then run through the iPhone side: notifications allowed for Monish in Settings, the Focus you have on, and the quiet hours and Live Activities set in the app’s Settings. While you’re typing in the terminal, a request arrives as a silent note on purpose, so test from a few steps away. The support page lists the rest.

Questions

Why does my Notification hook fire so late?
By design: permission_prompt waits about six seconds without a keystroke, idle_prompt about sixty seconds after Claude finishes. For a signal at once, use PermissionRequest or Stop.
Why doesn’t my Stop hook run when I press Esc?
Stop doesn’t run when you interrupt Claude. A turn that ends on an API error fires StopFailure instead.
Why does /hooks show nothing when my file looks right?
Usually invalid JSON, such as a trailing comma, or two hooks keys in one file. If the JSON is valid, restart the session, and check whether your organization allows only managed hooks.
Why does my osascript notification never show on macOS?
macOS shows it as coming from Script Editor, and drops it silently if Script Editor isn’t allowed to notify. Turn notifications on for Script Editor in System Settings.

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