PushNotification reports "Remote Control inactive" in sessions started with claude rc

Status Fixed / completed
Reported on v2.1.286
Maintainer reply None cached
Activity 0 comments · opened Oct 5, 2026 · closed Oct 6, 2026

Summary

In a session started with claude rc (Remote Control) and attached from the Claude mobile app, the PushNotification tool always reports Mobile push not sent (Remote Control inactive)., so completion alerts never reach the phone. The phone app has notifications enabled.

Environment

  • Claude Code 2.1.286, macOS (Apple Silicon)
  • Session launched inside tmux: tmux new -s <name> → claude rc
  • The conversation runs in the child process spawned by claude rc (--print --sdk-url .../v1/code/sessions/...). Its environment includes CLAUDE_CODE_ENVIRONMENT_KIND=bridge, CLAUDE_CODE_CHILD_SESSION=1, CLAUDE_CODE_ENTRYPOINT=sdk-cli, CLAUDE_CODE_SESSION_ATTENDED=0.

Steps to reproduce

  1. In tmux, run claude rc and attach to the session from the Claude mobile app.
  2. Have Claude call PushNotification (e.g. after a background task finishes, while the app is closed).

Expected

A push notification on the phone.

Actual

Tool result: Mobile push not sent (Remote Control inactive). This happened on every attempt over several days. When the user was actively viewing the session, the tool instead returned Not sent — this terminal is active ..., so attendance detection works, but Remote Control is not detected from the child session.

Suspected cause

The PushNotification tool in the bridge child session does not see the parent claude rc Remote Control connection.

View original on GitHub ↗