Dinoradar  /  Blog  /  Notifications
WorkflowBy Updated July 20266 min read

How to get notified when Claude Code needs you

The whole point of an agent is to walk away while it works. The catch: it stops and waits on you — and you don't find out for ten minutes. Here's how to close that gap.

THE GAP YOU DON'T SEE Claude working waiting on you… you're back wasted minutes A good notification collapses the red block to seconds. The signal is easy. Making it un-missable is the hard part.

The short answer

  • Built in: Claude Code can ring the terminal bell or fire a system notification when a turn ends — enable it in settings. Basic, but real.
  • The gap: those signals don't separate "needs you" from "done", are easy to miss, and don't say which session pinged.
  • The fix: a persistent, stateful alert that distinguishes waiting vs finished and clicks you back to the exact terminal.
  • Why it matters: the value of an agent is walking away — worthless if you don't learn it stopped until ten minutes later.

What Claude Code can do out of the box

Claude Code isn't silent. In its settings you can turn on a notification so that when it finishes a turn — or pauses to ask you something — it plays a terminal bell or fires a basic system notification. On some terminals (iTerm2, for instance) that surfaces as a native macOS banner.

For a single session you're half-watching, that's often enough. The problems start the moment you actually use the agent the way it's meant to be used: start it, switch away, do something else.

Why the built-in signal is easy to miss

  1. It doesn't distinguish states. "Blocked on a permission prompt" and "task complete" feel identical — a bell is a bell. You can't tell whether to rush back or relax.
  2. It doesn't persist. A bell rings once; a toast fades in seconds. Miss the instant and there's nothing left to notice.
  3. It's per-terminal. Run three sessions across iTerm and VS Code and a ping tells you something happened — not which one.
  4. It doesn't bring you back. Even when you notice, you still have to find and focus the right window yourself.
The real cost isn't the alert — it's the return trip. Noticing is half the job. The other half is landing back in the exact terminal, in the right state, without hunting. A good notification does both.

What a better notification looks like

This is the job Dinoradar's overlay is built for. It watches all your Claude Code sessions from the menu bar and shows a small floating alert that behaves the way you'd want:

  • Stateful. It turns red and calls you back only when Claude is actually blocked on you — a permission prompt, a question, a plan approval. Plain "still working" stays quiet and recedes.
  • Persistent. It stays until you deal with it, so a missed instant doesn't mean a missed session.
  • One click back. Clicking the alert focuses the exact terminal that needs you — iTerm, Terminal, VS Code, Ghostty or Warp.
  • Optional sound. Turn on an audible cue for the "needs you" state if you want to be pulled back from another app entirely.
  • Distinct "done". A finished task gets its own calm signal — not the same alarm as being blocked.

The design goal is attention calibration: recede while Claude is productive, come forward the instant it isn't. You get the freedom to walk away without the tax of constantly checking.

Walk away, actually. Dinoradar turns "let me just keep an eye on it" into "I'll know the second it needs me." Free forever. Try it free →

Related reading

While you're at it, the same monitoring that catches a waiting session also catches a runaway loop that's burning money — and helps you read your usage so you know where the time and cost actually go.

Frequently asked

Can Claude Code notify me when it needs input?+

Yes, basically. It can play a terminal bell or fire a system notification when a turn ends or it's waiting, configurable in settings. The catch: those signals don't distinguish "blocked on you" from "just finished", are easy to miss, and don't say which of several sessions needs you.

Why do I keep missing when Claude Code is waiting?+

The signal lives in the terminal. Switch to another window while Claude works — the whole point of an agent — and a bell or single toast is easy to miss, with nothing left to notice. You return minutes later to find it was blocked the whole time.

How do I get an alert when Claude Code finishes?+

Enable Claude Code's built-in notification for a basic ping, or use a menu-bar monitor like Dinoradar that shows a persistent overlay distinguishing "needs input" from "done", with an optional sound and a click straight back to the terminal that finished.

Does the notification work across multiple terminals?+

Built-in terminal signals are per-window, so with several sessions open you can't tell which pinged. Dinoradar watches all your sessions at once and its alert names the session and jumps you to the right terminal — iTerm, Terminal, VS Code, Ghostty or Warp.

Never miss when Claude Code needs you.

Dinoradar's overlay watches every session and pulls you back the instant one is blocked — one click to the exact terminal. Free forever · Pro $29 once.

Download Dinoradar — free More guides →