Remote Control: session should persist across disconnections

Problem

When using Remote Control (claude --remote), the session becomes unresponsive after ~5 hours of inactivity. The connection drops silently, and there is no way to reconnect to the same session.

This means:

• All conversation context is lost
• The user must start a new session and rebuild context from scratch
• The core value proposition of Remote Control (resume anytime from mobile) is undermined

Expected Behavior

Remote Control sessions should survive temporary disconnections. When a user reconnects via claude.ai, they should be able to resume the same session with full context preserved — similar to how claude --continue / claude --resume works for local CLI sessions.

Current Workaround

• Write a handover file before leaving the session (manual, lossy)
• Use autonomous.sh for long-running tasks instead (but loses the interactive benefit)

Suggested Solutions (any of these would help)

1. Session persistence: Keep the CLI-side session alive and allow reconnection from claude.ai
2. Auto-reconnect: If the WebSocket/SSE connection drops, re-establish it without losing session state
3. --resume for remote sessions: Allow resuming a remote session the same way local sessions can be resumed

Environment

• macOS 11 (Big Sur)
• Claude Code CLI (latest)
• Claude Max plan

Impact

This is the #1 friction point for mobile-first users who rely on Remote Control for async workflows throughout the day.