`claude rc` errors with "Workspace not trusted" instead of showing the trust dialog like `claude --remote-control`

What happened

When I start a remote control connection with the short command:

claude rc

in a workspace I have not yet trusted, it fails immediately with:

Error: Workspace not trusted. Please run `claude` in /home/spe/myproject first to review and accept the workspace trust dialog.

If I instead run the long form in the same directory:

claude --remote-control

I get the interactive workspace trust confirmation dialog, accept it, and the session starts fine. After that, claude rc also works.

Expected

claude rc should show the same trust confirmation dialog that claude --remote-control shows, rather than erroring out and telling me to run a separate command first. The two commands appear to be aliases for the same feature, so their trust-handling behavior should match.

Actual

claude rc refuses to prompt for trust and errors instead. The user has to run a different command (claude --remote-control, or plain claude) once to get through the trust dialog before claude rc will work.

Steps to reproduce

1. In a workspace that has not been trusted yet, run claude rc.
2. Observe the "Workspace not trusted" error.
3. Run claude --remote-control in the same directory.
4. Observe the trust dialog appears; accept it.
5. claude rc now works.

Environment

• Claude Code version: 2.1.210
• OS: Linux (WSL2, 6.18.33.1-microsoft-standard-WSL2)
• Shell: bash