remote-control fails: --sdk-url passed as Node flag instead of script argument

Resolved 💬 3 comments Opened Feb 26, 2026 by catchkyle Closed Mar 3, 2026

Description

claude remote-control fails immediately with node: bad option: --sdk-url. The --sdk-url flag is being passed as a Node.js runtime flag rather than as an argument to the CLI script.

Steps to Reproduce

claude remote-control

Error Output

[07:11:58] Session failed: /Users/kyle/.nvm/versions/node/v20.20.0/bin/node: bad option: --sdk-url session_01HX9QgT5a8BzwhJkiKV8huY
[07:11:58] To reconnect: claude --resume session_01HX9QgT5a8BzwhJkiKV8huY

Also reproduces with Node v25.6.0:

[07:16:52] Session failed: /opt/homebrew/Cellar/node/25.6.0/bin/node: bad option: --sdk-url session_018LDT8iwcV44LCN7WJj3VUu
[07:16:52] To reconnect: claude --resume session_018LDT8iwcV44LCN7WJj3VUu

The session connects successfully initially, then fails when spawning a subprocess — --sdk-url is placed in the Node flags position rather than as a script argument.

Environment

  • Claude Code version: 2.1.59
  • Node versions tested: v20.20.0 (nvm), v25.6.0 (Homebrew) — both fail
  • OS: macOS Darwin 24.6.0 (arm64)
  • Installation: npm install -g @anthropic-ai/claude-code
  • Shell: zsh

View original on GitHub ↗

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