Windows: claude remote-control fails with 'bad option: --sdk-url' (npm version)
Resolved 💬 4 comments Opened Mar 21, 2026 by Fulin938975 Closed Mar 25, 2026
Bug Description
claude remote-control via npm-installed Claude Code on Windows fails with:
[11:03:56] Session failed: C:\nvm4w\nodejs\node.exe: bad option: --sdk-url session_01LrMaTwMDgiDGXLwQBip48X
Environment
- OS: Windows 10
- Claude Code (npm): v2.1.59 (via
npm i -g @anthropic-ai/claude-code) - Claude Code (native): v2.1.81
- Node.js: v22.x (via nvm4w)
- Plan: Claude Max
Steps to Reproduce
- Install via npm:
npm i -g @anthropic-ai/claude-code - Run:
claude remote-control - Error:
Session failed: C:\nvm4w\nodejs\node.exe: bad option: --sdk-url
Workaround
Using the native installer version (claude.exe remote-control) works, but the npm version does not.
Additional Context
- The native version (v2.1.81) from
%APPDATA%\Claude\claude-code\2.1.51\claude.exeworks correctly - The npm version (v2.1.59) appears to pass
--sdk-urlas a Node.js flag instead of an application flag - Related issue: #37058 (Windows --channels also broken)
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗