Mobile push notifications not delivered despite "Mobile push requested" success response

Resolved 💬 4 comments Opened Apr 20, 2026 by kdantuono Closed Apr 22, 2026

Summary

PushNotification tool consistently returns Terminal notification sent. Mobile push requested. but notifications never arrive on the paired iOS device. Terminal notifications work correctly.

Environment

  • Claude Code: 2.1.114
  • OS: Linux 6.11.11-valve27-1-neptune (Steam Deck, SteamOS)
  • Shell: bash
  • iOS device: Claude app installed, logged in with same account, Remote Control connected (confirmed — the terminal session is visible and controllable from the phone)

Expected behavior

Push notification arrives on iOS device when tool reports Mobile push requested.

Actual behavior

Notification never arrives on the phone. Tool always returns success. Terminal notification fires normally.

Verification already performed

  • App-level notification toggles (Ricerca completata, Risposte chat, Aggiornamenti Code, Messaggi Dispatch) all ON
  • iOS Settings → Claude → Notifications: Allow Notifications ON; Lock Screen / Notification Center / Banners all checked; Banner style Temporary; Sounds ON; Badges ON
  • iOS Settings → Claude: Background App Refresh ON, Cellular Data ON
  • No Focus / Do Not Disturb / Scheduled Summary active
  • Force-quit and relaunched the Claude app (swipe away from multitasking) — issue persists
  • settings.json (global + all project-level) validated as proper JSON; no push-related keys present (never configured via /config — but the relevant option was confirmed enabled in /config)
  • /status not usable to inspect mobile registration (/status isn't available over Remote Control)

Repro

  1. From CLI session, trigger PushNotification (e.g. by asking the assistant to send a test push)
  2. Tool returns Terminal notification sent. Mobile push requested.
  3. Nothing appears on the paired iOS device — ever

The request/response cycle succeeds from the tool's perspective, so the failure is downstream (device-token registration, push provider delivery, or session-to-device routing).

Impact

Makes Remote Control effectively useless for the "get notified when the long-running task finishes" use case — the primary purpose of mobile push integration — on a paid plan.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗