[BUG] Running prompt with --remote-control order

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When running claude "<prompt>" --remote-control (or --rc), Claude executes the
prompt in print/non-interactive mode first, and only then opens the Remote Control
session. This means the initial prompt runs before the RC URL/QR code is displayed,
so you can't see the initial prompt on another devices when the response comes in.

What Should Happen?

Remote Control session should start first (showing the URL/QR code), then the prompt
should be handled within that RC session — so it's visible on connected remote devices.

If user asked for remote control it doesn't make sense to exclude the initial prompt from the session history on other devices.

Error Messages/Logs

Steps to Reproduce

1. Run: claude "some prompt" --rc
2. Observe: Claude answers the prompt in the terminal (print mode)
3. RC session opens after the prompt has already been answered

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.84 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_