← ClaudeAtlas

notify-setuplisted

Use when the user wants Claude Code to reach them on their phone, or phone notifications have stopped arriving — 'notify me on my phone', 'send notifications to my phone', 'set up push notifications', 'set up Pushover', 'ping me when Claude needs input', 'I keep missing when Claude finishes', 'phone alerts for Claude', 'notifications stopped working', 'make notifications less noisy', 'change notification priority', 'turn off phone alerts'. Requires the Notification hook event; on a harness without one it says so plainly instead of half-configuring.
Tamircohen28/tamirs-superpowers · ★ 2 · AI & Automation · score 74
Install: claude install-skill Tamircohen28/tamirs-superpowers
# notify-setup Configure phone push notifications for Claude Code via [Pushover](https://pushover.net). ## Platform support — check this first **This is a platform-specific capability, not a universal one.** It is built on Claude Code's `Notification` hook event: the harness fires a hook when the agent needs attention, and that hook pushes to the phone. Be precise about what is missing elsewhere. Several targets *do* have lifecycle hooks of some shape — the registry records Codex CLI's manifest `hooks` field as native and Cursor's as partial. What none of them has is an **agent-needs-attention event**. Without that event there is no moment to fire on, so a correctly-wired hook would simply never run. | Target | Status | Why | |---|---|---| | Claude Code | supported | Native `Notification` hook event | | Claude Desktop | unverified | Same plugin artifact, but the registry marks its `hooks` status `unknown` — whether the plugin hook bundle fires in Desktop sessions has not been verified. Do not claim it works; verify first | | Codex CLI | unsupported | Has manifest hooks, but not in Claude's shape and with no needs-attention event | | Cursor | unsupported | Claude-shaped plugin hooks do not run under a Cursor plugin install, and there is no needs-attention event | | Gemini CLI, OpenCode | unsupported | Registry marks hooks `unknown` and `unsupported` respectively; no needs-attention event either way | **Before step 1**, confirm the `hooks` capability for the current platf