Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] CLI and VS Code extension conflict on Windows — extension unusable until CLI is uninstalled

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

On Windows 11, when both the Claude Code CLI (via npm) and the VS Code extension are installed simultaneously, there is a conflict between them. The user was unable to use the Claude Code VS Code extension normally until the CLI was uninstalled.

Root Cause

On Windows 11, when both the Claude Code CLI (via npm) and the VS Code extension are installed simultaneously, there is a conflict between them. The user was unable to use the Claude Code VS Code extension normally until the CLI was uninstalled.

Fix Action

Workaround

Uninstall the CLI and use only the VS Code extension.

RAW_BUFFERClick to expand / collapse

Description

On Windows 11, when both the Claude Code CLI (via npm) and the VS Code extension are installed simultaneously, there is a conflict between them. The user was unable to use the Claude Code VS Code extension normally until the CLI was uninstalled.

Steps to Reproduce

  1. Install the Claude Code VS Code extension
  2. Install Claude Code CLI globally (via npm)
  3. Try to use the extension in VS Code
  4. Expected: extension works normally
  5. Actual: extension behavior is broken/unresponsive until CLI is removed

Environment

  • OS: Windows 11 Home (10.0.26100)
  • VS Code extension only (after uninstalling CLI, everything works fine)

Workaround

Uninstall the CLI and use only the VS Code extension.

Notes

This may be related to other conflict reports like #20546 and #22304, which describe CLI/extension conflicts around IPC/named pipes and browser extension connectivity. However this specific case is about the VS Code extension being unusable when the CLI is installed on the same machine.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING