[BUG] claude remote-control fails with "node: bad option: --sdk-url"

Resolved 💬 3 comments Opened Feb 26, 2026 by yuko-tamura Closed Feb 26, 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?

claude remote-control fails immediately with a node error. The command exits with "Session failed" and node reports --sdk-url as a bad option.

What Should Happen?

A remote control session should start and display a QR code or URL to connect from another device.

Error Messages/Logs

[20:24:45] Session failed: /Users/namename/.nvm/versions/node/v22.22.0/bin/node: bad option: --sdk-url session_XXXXXXXXXXXXXXXXXXX
[20:24:45] To reconnect: claude --resume session_XXXXXXXXXXXXXXXXXXX

Steps to Reproduce

  1. Run claude remote-control in any directory
  2. Session immediately fails with the error above

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.59 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

  • Node.js version: v22.22.0 (via nvm)
  • Tried with both /usr/local/bin/node (v20.9.0) and nvm node v22.22.0 - same error
  • Pro plan subscriber
  • It appears node is being called with --sdk-url as a node flag rather than as a script argument

View original on GitHub ↗

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