Does Claude Code have built-in push notifications?

Recent Claude Code releases added mobile push notifications tied to the official Claude app and Remote Control. They cover Anthropic-managed flows; for sessions on your own servers, hooks or an SSH client with notifications (like ServerCC) fill the gap.

Can I get notified and then act on the session from my phone?

Most notification setups stop at the ping: you know the run finished, but you still need a terminal to do anything about it. In ServerCC the notification opens a full terminal attached to the same tmux session.

Claude Code mobile notifications: three ways to know when it’s done

2026-07-17

Long Claude Code runs spend most of their time not needing you, then stop and wait: a plan needs approval, a question needs an answer, a diff needs review. If you don't notice, nothing happens until you do. A notification solves half of the problem. The other half is what you can actually do about it from the phone once it arrives.

Option 1: DIY with hooks + ntfy

Claude Code exposes hooks that fire on lifecycle events. Point a Stop hook at a push service like ntfy.sh and your phone buzzes when the agent stops:

{
  "hooks": {
    "Stop": [{
      "hooks": [{
        "type": "command",
        "command": "curl -s -d 'Claude Code finished' ntfy.sh/your-topic"
      }]
    }]
  }
}

Pros: free, transparent, works everywhere. Cons: per-machine setup you must maintain, no context in the ping, and acting on it still means finding a terminal and re-attaching by hand.

Option 2: official push notifications

Recent Claude Code releases added push notifications through the official Claude app, paired with Remote Control. If your workflow already runs through Anthropic-managed sessions, this is the zero-setup answer — and it will keep improving. Its scope is the official flow: sessions the Claude app can see, with interaction shaped like Remote Control, not a raw terminal on your own box.

Option 3: ServerCC — notification plus a terminal

ServerCC runs your agents in tmux on your own server and notifies you when a run completes. Tapping the notification opens a full terminal attached to that session, so you can approve the plan, type an answer, review the git diff, or hand the task to another parallel instance in Agent View.

Which one should you use?

If everything runs through Anthropic-managed sessions, use the official push — there is nothing to set up.
If you prefer to own each piece of the setup, hooks + ntfy is cheap and scriptable.
If your agents run on your own servers and you also want to act on the notification, ServerCC covers notification, terminal, diff review and parallel sessions in one app.

They also compose: plenty of users keep a ntfy topic for CI while ServerCC handles the interactive loop. Setup takes five minutes — Quick Start.