remote-control fails: node: bad option: --sdk-url

Resolved 💬 2 comments Opened Mar 1, 2026 by Egon91 Closed Mar 1, 2026

Bug Report

claude remote-control connects successfully but then immediately fails when spawning the child session process.

Error

[17:24:37] Session failed: /opt/homebrew/Cellar/node@20/20.20.0/bin/node: bad option: --sdk-url session_01Kz626KUPWe8zKYSRANzDeB
[17:24:37] To reconnect: claude --resume session_01Kz626KUPWe8zKYSRANzDeB

Steps to Reproduce

  1. Run claude remote-control
  2. Session connects and displays URL
  3. After a few seconds, the session fails with the above error

Environment

  • Claude Code version: 2.1.63
  • Node.js: v22.22.0 (also reproduced with v20.20.0)
  • OS: macOS 15 (Darwin 25.0.0), Apple Silicon (arm64)
  • Install method: Homebrew (/opt/homebrew/bin/claude)

Analysis

It appears that when Claude Code spawns a child process for the remote session, --sdk-url is being passed as a Node.js flag rather than as an application argument. Node interprets it as an unknown option and exits.

The child process seems to be invoked as:

node --sdk-url session_01Kz...

instead of:

node <script> --sdk-url session_01Kz...

This happens with both Node 20 and Node 22, so it does not appear to be Node-version-specific.

View original on GitHub ↗

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