[Feature Request] Allow `claude remote-control` to work via Dispatch (Claude Desktop) without re-authentication

Problem

When using Claude Desktop's Dispatch feature to start claude remote-control in a code task, it fails because:

1. Claude Desktop automatically sets CLAUDE_CODE_OAUTH_TOKEN environment variable, which is an inference-only token
2. remote-control requires a full-scope login token from claude login
3. Even if the user has recently run claude login, the CLAUDE_CODE_OAUTH_TOKEN env var takes precedence and overrides it
4. OAuth tokens from claude login expire after 8-12 hours, making it impractical to pre-authenticate before going out

Desired Behavior

Users should be able to start claude remote-control from Dispatch (or code tasks spawned by Dispatch) without needing manual terminal access. This would enable a powerful workflow: controlling Claude Code remotely from a phone via Dispatch.

Use Case

A developer wants to:

1. Leave their Mac at home/office
2. Open Claude Desktop on their phone (Dispatch)
3. Start claude remote-control on a specific project remotely
4. Do development work with Claude from anywhere

This is incredibly close to working but blocked by the authentication scope limitation.

Suggested Solutions

• Allow Dispatch/Claude Desktop to pass a full-scope token to code tasks
• Or allow remote-control to work with the token that Claude Desktop already provides
• Or implement longer-lived tokens for claude login that persist across sessions

Environment

• Claude Code version: 2.1.87
• Using Claude Desktop (Dispatch feature)
• macOS