Kicked off a Claude Code session, walked away, came back 2 hours later. Frozen on a permission prompt the whole time. Nothing got done.
Here’s the 5-minute fix that ended that for me.
The setup
Install ntfy on your phone, subscribe to a topic (e.g. <code>yourname-abc123</code>), then drop this in <code>~/.claude/settings.json</code>:
<pre><code>{
 &quot;hooks&quot;: {
 &quot;Notification&quot;: [{
 &quot;matcher&quot;: &quot;.*&quot;,
 &quot;hooks&quot;: [{
 &quot;type&quot;: &quot;command&quot;,
 &quot;command&quot;: &quot;curl -s -d &#x27;Check Claude&#x27; ntfy.sh/YOUR_TOPIC &gt; /dev/null&quot;
 }]
 }]
 }
}
</code></pre>
The <code>Notification</code> hook fires on permission prompts and idle — exactly when you need to know. No account needed for ntfy, just keep the topic name random enough.
This pairs especially well with Claude Code’s Remote Control. The whole point of remote control is kicking off a task locally and monitoring it from your phone — but without notifications, you still have to keep the app open and watch for prompts yourself. With this hook, the workflow actually closes: start a session at your desk, switch to Remote Control, walk away, and let ntfy tell you when Claude needs you. Your phone becomes the interrupt handler.
Now I kick off a task, go do something else, and my phone tells me when I’m actually needed. That’s it.

David Huang

A quick workflow tip for Claude Code users who lose time waiting on permission prompts. By configuring a Notification hook in ~/.claude/settings.json to send a curl request to ntfy.sh, developers get instant push notifications on their phone whenever Claude needs attention. This pairs with Claude Code's Remote Control feature to create a fully hands-off workflow: start a session, walk away, and only return when notified.

Stop babysitting your Claude: simple push notification fix