Remote Control sessions cannot survive a reboot / cannot re-attach from mobile

Type: Feature request + friction report
Environment: Claude Code v2.1.197, Windows 11, settings.json has "remoteControlAtStartup": true

What happens
A Remote Control session (driven from the Claude mobile app "Code" tab) is tied to the live local claude process. After the desktop reboots — necessarily offline for >10 min — the session times out server-side and cannot be reconnected. claude remote-control --continue reports the session no longer exists and starts a fresh one. So after every reboot I must start a brand-new session and lose continuity of the one I was controlling from my phone; the mobile app shows the old session as "disconnected" with no way to revive it.

Secondary bug
Running claude remote-control non-interactively (from a startup .cmd/script) fails with Error: Workspace not trusted. Please run 'claude' in <dir> first… even though ~/.claude.json already has "hasTrustDialogAccepted": true for that workspace. This blocks auto-starting Remote Control at login. (Clearing CLAUDECODE* env vars did not help.)

Requests

1. Persistent/resumable Remote Control sessions that survive a reboot — re-attach to the same session from mobile (a session id that outlives the process/offline window), or at least a much longer server-side timeout.
2. A supported non-interactive way to start Remote Control at login that respects the already-accepted workspace trust.

Why it matters
Seamless "continue on my phone after I reboot the shop PC" would make the daily workflow dramatically nicer.