[BUG] Desktop (Windows): Remote Control is not restored after the app restarts for an auto-update, so idle sessions get paused and become unreachable

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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?

When Claude Desktop installs an update, it quits and restarts on its own, often at night. On restart, it does not reconnect Remote Control for sessions that had it enabled. About 15 minutes later, the idle timeout pauses those sessions, because the pause is only skipped while Remote Control is active. From the phone or claude.ai/code, the sessions are then unreachable until I open the desktop app and turn Remote Control on again by hand. "Connect new sessions to Remote Control" is on. The machine stays awake and online the whole time.

### What Should Happen?

Sessions that had Remote Control enabled before an update restart should reconnect to Remote Control automatically after the restart. Then the idle-pause exemption keeps applying and the sessions stay reachable.

### Error Messages/Logs

From `%LOCALAPPDATA%\Claude\logs\main.log` (session IDs shortened):

```
2026-09-17 22:08:42 [info] [CCD] Skipping pause for session local_c4bb… - remote control is active (explicit bridge)
2026-09-17 23:40:41 [info] [CCD] Killing 4 PTY process tree(s) on quit
2026-09-17 23:40:42 [info] beforeQuitForUpdate handler fired, going down for update
2026-09-17 23:40:46 [info] Starting app {
2026-09-17 23:40:47 [info] [updater] Version changed since last launch: 2.110.1 → 2.2553.0
2026-09-17 23:56:13 [info] [WarmLifecycle:session] Idle timeout reached, disconnecting local_c4bb…
2026-09-17 23:56:13 [info] [CCD] Pausing session local_c4bb… (idle_timeout)
2026-09-18 06:10:05 [info] LocalSessions.toggleRemoteControl: sessionId=local_c4bb… enable=true
```

Between the restart and the manual toggle there are no "Enabling remote control" lines. The same update restarts happened on 2026-09-11 01:55, 2026-09-12 00:05 and 2026-09-13 23:01.

### Steps to Reproduce

1. On Windows, enable "Connect new sessions to Remote Control" and have a Code session with Remote Control connected.
2. Leave the app idle until it restarts to install an update ("going down for update" in main.log).
3. After the restart, check the session from the phone or claude.ai/code. Remote Control is off, and after the idle timeout the session is paused.

### Claude Model

Opus

### Is this a regression?

I don't know

### Last Working Version

_No response_

### Claude Code Version

2.1.274 (Claude Desktop 2.2553.0.0, Microsoft Store/MSIX)

### Platform

Anthropic API

### Operating System

Windows (Windows 11 Home, 10.0.26200)

### Terminal/Shell

Other (Claude Desktop app, Code tab)

### Additional Information

This report was drafted with Claude Code from the desktop app's main.log and reviewed by me before posting.

Start with the update-restart sequence shown in main.log, especially beforeQuitForUpdate and the post-launch startup path. Trace how LocalSessions.toggleRemoteControl and the WarmLifecycle:session idle timeout relate to the persisted Remote Control state. Done means sessions enabled before an update reconnect automatically after restart and remain reachable past the idle timeout.

Written by the indexing model from the issue text.