[BUG] remote-control fails: bridge spawns node with missing script path

Resolved 💬 3 comments Opened Mar 4, 2026 by cryptosisk Closed Mar 7, 2026

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 remote-control, the bridge successfully registers with
the Anthropic API and creates a session, but then fails immediately when
spawning the local claude subprocess. The bridge passes CLI flags directly
to node as node arguments, without including the path to cli.js. This causes
node to reject --sdk-url as an unrecognized option and exit with code 9.

What Should Happen?

The bridge should spawn the subprocess as:
node /path/to/cli.js --print --sdk-url wss://... --session-id ...

Instead it is spawning:
node --print --sdk-url wss://... --session-id ...

The script path (cli.js) is missing from the spawn call in bridgeMain.

Error Messages/Logs

[bridge:session] Child args: --print --sdk-url wss://api.anthropic.com/v1/session_ingress/ws/session_01AGgM6rcmnnzPLSaYS8wTcG --session-id session_01AGgM6rcmnnzPLSaYS8wTcG --input-format stream-json --output-format stream-json --replay-user-messages --debug-file /tmp/rc-debug-session_01AGgM6rcmnnzPLSaYS8wTcG.log
[bridge:session] sessionId=session_01AGgM6rcmnnzPLSaYS8wTcG failed exit_code=9 pid=77403
[ERROR] Error: Bridge session failed: /usr/local/bin/node: bad option: --sdk-url

Steps to Reproduce

  1. Install @anthropic-ai/claude-code@2.1.63 via npm
  2. Log in with claude auth login (claude.ai account, Max subscription)
  3. Run claude remote-control in any directory
  4. Session is created server-side but immediately fails locally
  5. Run claude remote-control --debug-file /tmp/rc-debug.log to confirm

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.63

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗