[BUG] Desktop: Remote Control drops on every idle session and can't be re-enabled until a message is sent from the Mac

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report
• [x] I am using the latest version of Claude Code

What's Wrong?

In the Claude desktop app (Code tab), Remote Control only stays connected while a session's process is running. Once a session finishes its turn and goes idle, the app shuts its process down, and the Remote Control link drops with it. The session then can't be reached from claude.ai/code or the mobile app until I go back to the Mac and send it a message there.

Today, of my 30 most recent local sessions, the 2 running ones had remoteControlActive: true and all 28 idle ones had remoteControlActive: false / remoteControlState: "off". "Connect new sessions to Remote Control" is on.

Trying to turn Remote Control back on for an idle session through the app's session tool (set_remote_control) is refused:

Remote Control requires an active session. Send a message first.

That defeats the main reason to use Remote Control: picking up a finished chat from my phone while I'm away from the Mac.

What Should Happen?

A session with Remote Control on should stay reachable from claude.ai/code and mobile after it goes idle. Sending it a message from my phone should wake its process, just like sending one from the desktop does. If idle processes have to be shut down, the Remote Control link should stay registered, or come back on its own, so the session doesn't silently drop off.

Error Messages/Logs

Remote Control requires an active session. Send a message first.

Steps to Reproduce

1. In the desktop app, turn on Settings > Claude Code > "Connect new sessions to Remote Control".
2. Start a local session and send a message. Remote Control shows as connected.
3. Let the turn finish and leave the session idle.
4. Open claude.ai/code or the mobile app: the session is no longer connected or reachable.
5. Back on the desktop, the session's Remote Control state reads "off". Turning it on is refused until a message is sent from the desktop.
6. Send any message from the desktop: Remote Control reconnects.

Claude Model

Opus

Is this a regression?

I don't know

Claude Code Version

2.1.300 (Claude Code), desktop app 2.42304.0

Platform

Anthropic API

Operating System

macOS 27.0.1

Terminal/Shell

Claude desktop app (Code tab)

Additional Information

Related but different: #33041 (CLI Remote Control disconnects) and #95339 (forked desktop sessions don't auto-connect). This one is about every idle desktop session losing Remote Control.