Remote control sessions should persist without interactive re-login

Problem

Remote control is designed for a common use case: leaving a machine running at home and controlling it from another device via claude.ai/code. But in practice, the OAuth token expires after a couple of days, killing the remote control session. Re-authenticating requires claude /login, which opens a browser on the host machine — defeating the purpose of remote access.

This makes remote control unreliable for its primary use case. Users end up needing SSH + Tailscale + launchd just to keep sessions alive, which is far too much setup for something that should work natively through the Claude account.

Expected behavior

• Remote control sessions should stay authenticated long-term (days/weeks, not hours)
• If a token does expire, it should refresh automatically without interactive login
• Alternatively, allow re-authentication from claude.ai/code itself — the user is already logged into the same account there

Current workaround

• SSH into the host machine and run claude /login to get a new token
• Requires the host machine to have SSH enabled and be reachable (same network or VPN)
• Not feasible when away from the home network without additional infrastructure (Tailscale, port forwarding, etc.)

Environment

• Claude Code v2.1.80
• macOS
• Pro plan, OAuth authentication