# How to Get a Notification When Claude Code Needs Input

> Configure the PingRoom CLI hook for Claude Code so completion, failure, permission, and input-needed lifecycle events can reach your phone.

- Published: 2026-08-02
- Author: PingRoom
- Category: Agents
- Topics: Claude Code needs input notification, Claude Code phone alert, notify when Claude Code finishes
- Canonical: https://pingroom.io/blog/claude-code-needs-input-notification
- Cover image: https://pingroom.io/blog/claude-code-needs-input-notification.webp
- Cover description: A dark coding terminal sending a focused red input request to a nearby phone.

PingRoom’s CLI includes a Claude Code hook that reads lifecycle events from standard input and turns selected moments into room Pings or Questions. That lets a long-running coding task call you back when it completes, fails, or reaches a bounded human decision.

## Generate the hook configuration

Install and authenticate the current PingRoom CLI, then print its Claude Code hook block:

```bash
pingroom hook --print-config
```

Set the credential or room webhook described by the CLI documentation, merge the printed `hooks` block into the appropriate Claude Code settings, and run a controlled test. Use the README included with the current CLI release for installation and configuration details, because hook event schemas and supported options can change.

## Notify on transitions, not logs

The useful events are the moments where a person can alter the outcome: a task finished and needs review, a run failed, a permission boundary needs a decision, or Claude Code stopped for input. Sending every tool call to the phone creates noise and trains you to ignore the room.

For an informational completion, send a plain Ping. For a bounded permission choice, use a Question and treat expiry or no response as no permission. A Handoff is better when the next step requires a browser session or nuanced human judgment.

Keep credentials in environment or secret storage, not in the hook config committed to a repository. Do not include source code, private prompts, or secrets in lock-screen notifications.

Read [Let Claude Code Ping You When It Needs You](/blog/claude-code-hook) for the design rationale and [agent access documentation](/documents/agent-access) for scoped identity.