Claude Code notifications
turn your Mac red when it needs you

Hook PermissionRequest, not Notification, and make it something you can't miss: this free script turns your screen red.

Download for MacmacOSSend it to your Mac
Claude Code notifications: turn your Mac red when it needs you
  • The usual Notification hook ran 6.6 seconds after Claude asked. PermissionRequest ran in 0.06.
  • In our runs PermissionRequest also caught all 13 of Claude's questions, though the docs don't promise it.
  • Copy one free script: your screen stays red, with the project's name, until you're back.

You switch to Slack. Claude asks one question and, as one GitHub issue puts it, “just sits there waiting while I’m doing something else.”

We sell an app for this. This post is the free way: one file, one hook, no account, and you never need our app to use it.

The usual hook runs late

Claude asks you something

PermissionRequest0.06 s
Notification6.6 s

Claude finishes

Stop0.03 s
Notification60 s

We ran real Claude Code and timed every hook. Its docs’ own desktop alert uses Notification, and so did the two top guides we read. The docs say why it’s slow: it waits about six seconds on a prompt, each keystroke pushes that back, and it waits 60 after a reply. Six seconds won’t ruin your day. But it’s long enough to be looking elsewhere, and then a banner slides away and you’ve missed it anyway.

One hook caught the questions too

That issue was closed with Anthropic’s answer: PermissionRequest for permission, PreToolUse on AskUserQuestion for questions. In our runs PermissionRequest alone fired for all 13 questions. The docs don’t promise that, so if questions ever stop turning your screen red, add the second hook.

So don’t send a banner. Turn the screen red.

Your screen goes red with the project’s name on it, and stays until you touch the keyboard or mouse. Clicks go through it and it never takes focus, so it can’t eat what you’re typing.

Set it up in five minutes

  1. Build it. You need Apple’s command line tools (xcode-select --install).
    Terminal
    curl -fsSL https://www.useyappr.com/blog/claude-code-notifications/claude-red.swift -o ~/.claude/claude-red.swift
    swiftc -O ~/.claude/claude-red.swift -o ~/.claude/claude-red
  2. Try it. Your screen goes red. Move the mouse to clear it.
    Terminal
    echo '{"cwd":"/my-project"}' | ~/.claude/claude-red
  3. Add the hook, merged into any you already have, then start a new session.
    ~/.claude/settings.json
    {
      "hooks": {
        "PermissionRequest": [
          {
            "hooks": [
              { "type": "command", "command": "pkill -x claude-red; ~/.claude/claude-red", "async": true }
            ]
          }
        ]
      }
    }

To remove it: delete that block and the two claude-red files.

Read the script first (it's 41 lines)
claude-red.swift
// claude-red: turns every screen red, with the project's name on it, until you
// next touch the keyboard or mouse. Hook input arrives as JSON on stdin.
import AppKit

let hook = (try? JSONSerialization.jsonObject(with: FileHandle.standardInput.readDataToEndOfFile())) as? [String: Any]
let project = URL(fileURLWithPath: hook?["cwd"] as? String ?? "Claude").lastPathComponent

let app = NSApplication.shared
app.setActivationPolicy(.accessory)           // no Dock icon, never takes focus

var windows: [NSWindow] = []
for screen in NSScreen.screens {
    let w = NSWindow(contentRect: screen.frame, styleMask: .borderless, backing: .buffered, defer: false)
    w.level = .screenSaver
    w.ignoresMouseEvents = true                // clicks go straight through
    w.collectionBehavior = [.canJoinAllSpaces, .fullScreenAuxiliary]
    w.backgroundColor = NSColor.systemRed.withAlphaComponent(0.5)
    w.isOpaque = false
    let label = NSTextField(labelWithString: project)
    label.font = .systemFont(ofSize: 96, weight: .bold)
    label.textColor = .white
    label.sizeToFit()
    label.setFrameOrigin(NSPoint(x: (screen.frame.width - label.frame.width) / 2,
                                 y: (screen.frame.height - label.frame.height) / 2))
    w.contentView?.addSubview(label)
    w.orderFrontRegardless()
    windows.append(w)
}

// Stay until the first key press, click or mouse move at least 1.5s after it appeared
// (or after the display woke, so the key that wakes it doesn't clear it unseen). 8 hours at most.
var start = Date()
let began = Date()
let anyInput = CGEventType(rawValue: ~0)!
Timer.scheduledTimer(withTimeInterval: 0.2, repeats: true) { _ in
    if CGDisplayIsAsleep(CGMainDisplayID()) != 0 { start = Date() }
    let shown = Date().timeIntervalSince(start)
    let idle = CGEventSource.secondsSinceLastEventType(.combinedSessionState, eventType: anyInput)
    if (shown > 1.5 && idle < shown - 1.5) || Date().timeIntervalSince(began) > 28800 { exit(0) }
}
app.run()

Where red is the wrong answer

You're away from your MacUse Remote Control’s “Push when actions required”. It goes to your phone.
You run many background sessionsclaude agents lists which are waiting, and you can answer there.
You'd rather not be asked at allAuto mode, now the default where it’s available, clears most prompts. Questions still stop and ask.
Two sessions wait at onceYou see only the latest name, and it goes red even if you’re watching that terminal.
You run claude -p in scriptsThe docs say this hook also fires when a run that can’t prompt is about to deny a call, so you may get red with nothing to answer.
You also want to know when it's doneAdd the same hook under Stop. With several sessions, expect a lot of red.

What we built after this

Red tells you who. It doesn’t tell you what, and you still have to go find that terminal. Yappr Agents sits on the same hooks and puts it on the notch: a ring for each session, the question itself over whatever app you’re in, and you click the answer or say it. It’s Mac only, and paid after the trial. If red is enough, keep red.

Hooks are good for more than this: if something must always happen, make it a hook. And here is Yappr Agents, in clips. Running this many sessions on branches? Don’t trust git’s date queries on main. Using Codex too? Its hooks stop running when you edit them.

How we measured, and what we didn't test

Claude Code 2.1.318 in a terminal on macOS 26.6.2, one MacBook, 5 November 2026. To script Claude’s replies without spending tokens we pointed it at a small local stand-in for the API, so time zero is when the stand-in finished replying. 10 runs each for a permission prompt and a question, 3 for a finished reply. Medians. With auto mode on (3 runs each) a routine command ran with no prompt and a question fired the hook as before, but against the stand-in the real auto mode check never ran.

The red window took about 0.35 s from launch to screen the first time and about 0.1 s after. The exact hook above started one window with the prompt still waiting, 10 runs out of 10, and the same hook under Stop started it once.

Not tested: VS Code or the desktop app, background sessions, two displays, a full-screen app, or a sleeping display. Files: the raw log, the launch times, the stand-in, the test driver, the script. Docs read the same day: hooks, agent view, Remote Control, permission modes.

Written 5 November 2026. Every fact about another product is from its own pages, checked that day.