PushNotification tool always returns "Remote Control inactive" from scheduled tasks and non-remote-control sessions

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

The PushNotification tool consistently returns Mobile push not sent (Remote Control inactive) when called from scheduled tasks or regular interactive sessions, even with a fully configured setup.

Environment:

• Claude Code version: 2.1.112
• OS: Windows 11
• Auth: claude.ai Pro (same account on mobile and desktop)
• Mobile: Official Claude app, signed in with same account

Steps to reproduce:

1. Install Claude Code v2.1.112, sign in via claude.ai (Pro account)
2. Install Claude mobile app, sign in with the same account
3. Enable "Enable Remote Control for all sessions" in /config
4. Create a scheduled task that calls the PushNotification tool (e.g. a daily news digest agent)
5. Run the scheduled task
6. Observe: Mobile push not sent (Remote Control inactive)

Also reproduced in regular interactive sessions — calling PushNotification from a normal claude session returns "Remote Control inactive" even after:

• Opening and force-quitting/reopening the Claude mobile app
• Signing out and back in on the mobile app
• Running claude remote-control in a separate terminal and successfully connecting via the mobile app

Push only works from within the active claude remote-control session itself, making the PushNotification tool completely unusable for background/scheduled tasks.

Related issue: #28765 (push notifications when app is backgrounded in remote-control mode) — our issue is distinct: push fails entirely from non-remote-control sessions, including scheduled tasks.

What Should Happen?

Push notifications should be delivered to any registered mobile device associated with the authenticated Claude account, regardless of whether the sending session is an interactive claude remote-control session or a background/scheduled task.

The primary use case for PushNotification in scheduled tasks (e.g. daily digests, build monitors, CI watchers) requires it to work without an active Remote Control terminal session running simultaneously.

Error Messages/Logs

Mobile push not sent (Remote Control inactive).

Steps to Reproduce

1. Install Claude Code v2.1.112, sign in via claude.ai (Pro account)
2. Install Claude mobile app, sign in with the same account
3. Enable "Enable Remote Control for all sessions" in /config
4. Create a scheduled task that calls the PushNotification tool
5. Run the scheduled task
6. Observe: "Mobile push not sent (Remote Control inactive)"

Also reproduced by calling PushNotification directly in a regular interactive claude session — same result even after connecting via claude remote-control in a separate terminal.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.112

Claude Code Version

2.1.112 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

The PushNotification tool description states: "If Remote Control is connected, it also pushes to their phone." This implies push is session-scoped to an active remote-control connection — but scheduled/background agents have no such connection.

For the PushNotification tool to be useful in automated workflows (its primary use case), it should push to any registered device for the authenticated account without requiring an active claude remote-control terminal session.

claude auth status:

• authMethod: claude.ai
• apiProvider: firstParty
• subscriptionType: pro
• email: confirmed same on mobile and desktop

Related: #28765 (push when app backgrounded in RC mode) — our issue is distinct: push fails entirely from non-RC sessions including scheduled tasks.