CLI flags issues on Windows
Issues the maintainers labelled both platform:windows and area:cli.
214 issues · 40 open · 174 resolved (81%) · first seen Feb 11, 2026
Is this getting better or worse?
This class of problem is holding steady. 56 new reports in the last 90 days vs 73 in the 90 before — -23%. The open backlog peaked at 48 in 2026-03 and sits at 40 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
165 of these reports name the Claude Code build they were running, spanning 98 releases. Heaviest reporters:
- Claude Code v2.1.80
- Claude Code v2.1.63
- Claude Code v2.1.81
- Claude Code v2.1.119
- Claude Code v2.1.286
- Claude Code v2.1.251
- Claude Code v2.1.74
- Claude Code v2.1.195
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 30 days across 174 closures. Of the 174 closures with a recorded reason, 22% were closed as completed and 136 as not-planned or duplicate. The most recent completed fix landed in 2026-09.
Workarounds reported by the community
48 of these issues post a workaround someone says worked. The highest-engagement ones:
- effortLevel setting doesn't support "max" value
- …a runtime command via and doesn't persist across sessions. Workaround — SessionStart hook to auto-remind: This sets the highest persistent level ( ) and reminds you at session start that is available for the current ses…
Found in the thread of #35904 · resolved - --dangerously-load-development-channels should support skipping the confirmation dialog
- …o human at the keyboard to press Enter. We've stacked Win32 workarounds today (~80 LOC) just to get through it: - shredded our PS init line on → switched to UTF-16LE base64 - Prompt blocked spawn → after + HWND snap by u…
Found in the thread of #42486 · still open - [BUG] /desktop fails on Windows when Claude Desktop is installed as MSIX/Store package (refile of #36079)
- Confirmed Workaround (tested on Windows 11 Pro, CLI 2.1.143, Store package 1.7196.0.0) Hit the same issue independently and found that a protocol-forwarding shim at the expected path fully resolves it. This also fixes a…
Found in the thread of #59692 · resolved - [BUG] /desktop fails on Windows - "Failed to open Claude Desktop" despite app being installed and running
- …de Desktop installation (partially fixed with HKLM registry workaround) 2. Session transcript path mismatch between CLI and Desktop app i think that Both need to be fixed on Anthropic's side.
Found in the thread of #59824 · resolved - /desktop command fails on Windows Store (MSIX) installation
- …path is not directly launchable via for Store apps. Working Workaround The Claude Desktop MSIX package registers the protocol handler. Launching via protocol URI works perfectly: This correctly opens the CLI session in t…
Found in the description of #59883 · resolved
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 1–100
Ranked by community engagement (reactions weighted over comments).
- effortLevel setting doesn't support "max" value
- Add remoteControlEnabled setting to auto-start /remote-control on session start
- [BUG]
- --dangerously-load-development-channels should support skipping the confirmation dialog
- [BUG] /desktop fails on Windows when Claude Desktop is installed as MSIX/Store package (refile of #36079)
- [BUG] /desktop fails on Windows - "Failed to open Claude Desktop" despite app being installed and running
- Remote Control not enabled for Max plan account
- /desktop command fails on Windows Store (MSIX) installation
- Remote Control not enabled despite active Max 20x subscription
- `claude` exits 1 when run with no args and no stdin, which blocks winget releases
- [BUG] claude --resume causes complete terminal freeze on v2.1.204
- claude doctor false positive: "~/.local/bin is not in your PATH" when it IS in PATH (own install dir stripped from spawned-shell PATH)
- /insights: file:// URL broken on Windows — backslash before .claude dropped, link not clickable
- [Feature Request] Add restart command to auto-resume conversation after updates
- [FEATURE] Custom system prompt support in desktop app and VS Code extension (parity with CLI --system-prompt-file)
- remote-control hangs on 'Connecting' — stale environments cannot be cleared
- Archive/delete of Claude Code sessions is per-client — desktop's archive flag is invisible to the VS Code extension
- Remote Control (/rc) feature not available — Windows 11, Claude Code v2.1.69
- [BUG] /copy command corrupts UTF-8 characters on Windows again (regression from #22346)
- PreToolUse hooks and --allowedTools not enforced in headless -p mode
- Remote Control fails on Windows npm install: node.exe bad option --sdk-url
- [BUG] Remote Control: "is not yet enabled for your account" persists for Max user across all documented troubleshooting steps
- [BUG] Remote Control regression - "not yet available on your plan" on Claude Max
- Remote Control: environment lifecycle — stale environments accumulate, are indistinguishable from live ones, and cannot be removed
- `--bg` feature gate disabled on Windows, enabled on macOS for same account + version
- [BUG] Regression after v2.1.112: silent CLI exits on Windows, not fully fixed by NODE_OPTIONS
- [BUG] --teleport only checks the origin remote, fails when the GitHub remote has a different name
- [BUG] Remote Control not yet enabled on Max plan after removing DISABLE_TELEMETRY
- Feature: Share scheduled tasks between CLI and Desktop
- [Windows] remote-control fails: "bad option: --sdk-url"
- [BUG] Claude Code CLI (`claude -p`) burns ~15-16k tokens of fixed overhead per call when used as a stateless batch text-completion backend
- claude auto-mode critique returns "No critique was generated" for a large autoMode block; works with a small one
- Remote Control no longer available — was previously working
- --dangerously-load-development-channels incompatible with remote-control subcommand
- [BUG]
- [BUG] Remote Control: sending from mobile silently fails (message disappears), reading works fine
- On resume, recent work is gone and the session reverts to the last rename point (CLI, Windows 11)
- /resume returns empty picker when launch-cwd encodes differently than original session cwd (path-encoding nondeterminism in fh())
- [BUG] claude_code.active_time.total not emitted in --print mode on 2.1.119
- [Bug] /effort auto command incorrectly defaults to MAX mode instead of auto
- [Bug] 1M context window not auto-applied on Max plan in Claude Code CLI v2.1.114 (plus: `--model` flag silently drops `[1m]` suffix)
- [SYS-034] v2.1.113 native binary switch terminates running sessions on upgrade — API Error: terminated
- [Feature Request] Add `/restart` command to reload Claude Code session without exiting
- [BUG] /insights command is BROKEN on Windows 11
- [BUG] Unrecognized slash commands moved from a free, deterministic rejection to a paid, highly variable model call, with cost rising undocumented across releases
- C:/Program Files/Git/remote-control and /rc commands broken in v2.1.195
- [BUG] Option to log issue in GitHub from Claude Code can fail silently
- [FEATURE] Computer Use support in Claude Code CLI on Windows
- Feature request: Unified session history sync across VS Code extension, desktop app, and CLI
- [BUG] remote control command unavailable on pro account using claude code version v2.1.133
- [BUG] remote control jams the workflow, work pauses indefinitely
- --channels flag never matches plugin server identifier — channel notifications always skipped
- [BUG] `--allowedTools` has no effect when permission bypass flags are active
- Slash-clear creates sessions invisible to slash-resume picker due to malformed file structure
- [BUG] Remote Control not enabled for Max 20x subscriber — two distinct errors
- Remote Control: host-targeted restart/update trigger for relay-only operators (re-file of the restart half of #53125)
- [BUG] Remote Control won't work when ANTHROPIC_AUTH_TOKEN or ANTHROPIC_API_KEY is set
- [BUG] claude -p silently exits with no output on Windows 11 (v2.1.131)
- Claude CLI subprocess silent-hang: zero stdout for 3+ minutes (intermittent)
- [BUG] [Windows] Claude Code 2.1.139 still hangs after all documented workarounds (spawn EINVAL, blank -p output, interactive hang)
- [BUG] /release-notes changelog cache not refreshing — stuck at 2.1.79 since March 2026
- [BUG] claude -p headless: no spend visibility/cap for orchestrated workloads -- $313 burned in 8.5h on a single retry-stuck item; support routing loop with 3 Fin contradictions
- [BUG] Ghost sessions created with unexpected stdin content on Windows when using subagents
- [Bug] Claude Code exits silently without error logging on Windows PowerShell
- # Malformed flag `-dangerously-skip-permissions` (single dash) silently enables `--debug` via prefix match
- Claude Code CLI fails on Windows when username path contains spaces
- [BUG] Non-interactive Claude Code (-p) cannot use existing Claude Pro login
- [BUG] v2.1.74 - Session resume crashes PowerShell + memory leak cascades to Claude Desktop (Windows non-admin) - CRITICAL !!!
- Windows: --resume silently fails for sessions created by older CLI version (npm to native migration)
- [BUG] Remote Control not enabled despite Max 5x plan - machine-specific
- [BUG] Remote Control fails with "Failed to convert session context" for self-hosted git remotes
- [Bug] Remote Control disabled for Max subscription account
- [BUG] /clear built-in command being intercepted as a skill lookup
- [BUG] Remote Control fails with "Bridge environments are not available for this organization" on Pro plan (Windows)
- Remote Control failed - Pro plan user on Windows
- [Bug] Remote Control feature unavailable on Pro plan despite account eligibility
- [Bug] Remote control functionality unavailable after update and restart
- Headless (-p) sessions launched via Windows Task Scheduler deny already-allowlisted tool calls (Bash/PowerShell/Write/Edit); identical manual invocation never fails
- [FEATURE] Allow redeeming the usage reset ticket ("Reset for free") from the CLI
- --channels: inbound notifications silently dropped from the very first message (Team plan) — looks like a regression of the 2.1.105 fix
- [BUG] remote-control rejects --agent, --append-system-prompt and --settings, so server-spawned sessions cannot be given a role at launch
- claude mcp add --header exposes Authorization/Bearer token value in stdout
- [FEATURE] Project switcher / change working directory within an active session
- [Bug] RemoteTrigger.list: API returns next_cursor but tool wrapper exposes no cursor input parameter (pagination unusable from CLI)
- CLAUDE_CODE_PROJECT_DIR env var silently ignored — session JSONL still writes to in-tree .claude/projects/ (CLI 2.1.144, Windows)
- [BUG] --resume picker does not show session when project path contains underscores
- [BUG] Claude Code remote control experiences frequent unrecoverable hangs
- Session resume fails with 'FKH is not a function' error in v2.1.120
- Add --remote-control flag to interactive sessions
- [BUG] /desktop command not recognized in CLI on Windows ARM64
- [BUG] Severe startup lag when launching from a git subdirectory (regression since v2.1.87)
- Custom agents via --agent flag silently ignored on Windows (2.1.87)
- Session resume fails immediately after logout
- [BUG] Claude Code CLI Cannot Run
- Remote control messages not persisted to local session JSONL
- [BUG] Remote Control not yet enabled for Pro account (Windows 11)
- [BUG] `claude update` blocks ~100s on telemetry POST before exiting
- Remote Control: phantom sessions cannot be closed
- [BUG] MCP Server Connection Fails on Windows — `cmd /c` wrapper corrupted by CLI parser
- Slash commands /chrome and /voice unreliable — inconsistent availability and silent failures