CLI flags issues on Windows — page 2

Issues the maintainers labelled both platform:windows and area:cli.

181 issues · 32 open · 149 resolved (82%) · first seen Feb 11, 2026

Is this getting better or worse?

This class of problem is converging. 50 new reports in the last 90 days vs 111 in the 90 before — -55%. The open backlog peaked at 48 in 2026-03 and sits at 32 today.

0 12 24 36 48 2026-022026-042026-062026-08
2026-02 — First reports2026-03 — Peak backlog (48 open)

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

136 of these reports name the Claude Code build they were running, spanning 79 releases. Heaviest reporters:

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 149 closures. Of the 149 closures with a recorded reason, 25% were closed as completed and 112 as not-planned or duplicate. The most recent completed fix landed in 2026-08.

Workarounds reported by the community

40 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 - "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
[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 · still open
/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 101–181

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. CLI flags issues on macOS

    431 issues
  2. CLI flags issues on Linux

    187 issues
  3. Terminal UI issues on Windows

    1,530 issues
  4. The desktop app issues on Windows

    1,503 issues
  5. Core CLI issues on Windows

    1,285 issues
  6. Tool calls issues on Windows

    891 issues
  7. Cowork issues on Windows

    872 issues
  8. IDE integration issues on Windows

    869 issues