Remote Control: session URL opens in browser instead of Claude mobile app, requiring re-authentication

Bug Report

Describe the bug

When using claude remote-control, the generated session URL (e.g. https://claude.ai/code/session_...) opens in the system browser instead of routing to the Claude mobile app. This forces the user to re-authenticate in the browser even though the Claude app is already installed and has an active authenticated session.

Expected behavior

The session URL should deep-link into the Claude mobile app directly, reusing the existing authenticated session — similar to how other services handle app deep-linking (e.g. Spotify, Notion, Linear).

Actual behavior

• URL opens in the browser
• Browser prompts for credentials
• Claude app is bypassed entirely despite being installed and logged in

Steps to reproduce

1. Have Claude app installed on mobile with an active session
2. Run claude remote-control on desktop
3. Copy or scan the generated URL/QR code on mobile
4. URL opens in mobile browser, not in the Claude app
5. Browser requests login credentials

Environment

• Platform: Linux (desktop)
• Claude Code version: 2.1.108 (Claude Code)
• Mobile OS: Android

Impact

This makes the remote control feature significantly harder to use. The whole point is seamless continuation from desktop to mobile — requiring re-authentication in the browser defeats that purpose.

Suggested fix

Implement a deep-link / universal link scheme (e.g. claude://remote-control/session_...) so the mobile OS routes the URL to the Claude app instead of the browser.