How to Fix Claude Not Working in VSCode | Won't Launch, IDE Not Detected

First Check: The /doctor Diagnostic Command and Prerequisites {#first-check}

Before diving into individual fixes, systematically narrow down the cause. If Claude Code launches, run /doctor in the prompt box. It automatically checks your installation status, configuration validity, MCP server settings, and context usage all at once. If claude won't launch at all, run claude doctor from your shell (terminal) for an equivalent diagnosis.

Also verify the prerequisites. The official requirements are:

1. VS Code 1.98.0 or later (check via Help → About)
2. An Anthropic account (sign in when you first open the extension)

One commonly overlooked factor is your subscription plan. The free Claude.ai plan does not include Claude Code — even with the extension installed, it won't launch. You need at least a Pro subscription or a Console account (API) at minimum. See the separate article "Claude in VSCode Pricing" for a breakdown of pricing options.

Source: Troubleshooting — Claude Code Docs / Using Claude Code in VS Code — Claude Code Docs

Extension Won't Install or Doesn't Appear {#install-fail}

If installation from the Marketplace fails, or the extension doesn't show up after installing, try these steps in order:

1. Check your VS Code version — 1.98.0 or later is required. Older versions will reject the extension with a compatibility error
2. Check installation permissions — Verify that you have permission to install extensions in VS Code (corporate machines may restrict this)
3. Install directly from the Marketplace — If searching in the extensions view doesn't work, try installing directly from the VS Code Marketplace page
4. Not showing after installation — Restart VS Code, or run "Developer: Reload Window" from the command palette (Cmd+Shift+P / Ctrl+Shift+P)

The same extension works in VSCode forks like Cursor, Windsurf, and Kiro. If the extension simply won't install in your editor, you can still use Claude as a CLI by running claude in the integrated terminal.

Source: Using Claude Code in VS Code — Claude Code Docs

Spark Icon Missing or Panel Won't Open {#no-spark-icon}

The extension is installed, but the Spark (✱) icon — the entry point for launching Claude — is nowhere to be found. This is the most common "not working" complaint. The Spark icon appears in the editor toolbar at the top right when a file is open. If it's not showing, try these steps in order:

1. Open a file — The icon won't appear if you've only opened a folder. Open any file in the editor
2. Check your VS Code version — Must be 1.98.0 or later (Help → About)
3. Reload the window — Run "Developer: Reload Window" from the command palette
4. Disable conflicting AI extensions — Temporarily disable other AI extensions like Cline or Continue
5. Check workspace trust — Extensions don't function in Restricted Mode. Re-open your workspace as a trusted workspace

If you still can't find it, an alternative entry point is to click "✱ Claude Code" in the status bar at the bottom right of the window — this works even without a file open. You can also type "Claude Code" in the command palette and select a launch command.

Source: Using Claude Code in VS Code — Claude Code Docs

Can't Sign In / "Please run /login" Won't Go Away {#signin-loop}

The panel opens but sign-in never completes, and "Not logged in · Please run /login" keeps appearing. Here's what to do:

1. Wait for the automatic re-prompt — When this message appears, the extension automatically re-opens the sign-in screen
2. Reload the window — If the sign-in screen doesn't reappear, run "Developer: Reload Window" from the command palette
3. Inherit environment variables — If you have ANTHROPIC_API_KEY set in your shell but are still being prompted to sign in, VS Code may not be inheriting the shell environment. Launch VS Code from your terminal with code . to carry over the environment variables, or sign in with your Claude account

As mentioned above, the free Claude.ai plan won't let Claude Code run even after successful authentication. If "sign-in worked but it still won't run," check whether your plan is Pro or higher (or a Console account).

Source: Using Claude Code in VS Code — Claude Code Docs

v2.1.51 Bug That Broke Launch for All Windows Users and How to Work Around It {#v2151-bug}

If it "worked fine yesterday but stopped after an update," suspect a known bug in the extension. Claude Code for VS Code v2.1.51, released in 2026, had a bug where a Linux build path was accidentally included in the Windows build, causing file loading to fail and preventing activation of the extension.

This was a structural bug — not a user error — and every Windows user encountered the same error. The frustrating part: reinstalling or restarting didn't help (the latest version would just reinstall the same bug). The workaround was to downgrade to a stable version:

1. Right-click on Claude Code in the extensions panel
2. Select "Install Another Version"
3. Install the confirmed stable version v2.1.49
4. Restart VS Code

To prevent recurrence, right-click the extension again and select "Disable Auto Update" (this doesn't affect auto-updates for other extensions). Your user data and conversation history are preserved after downgrading. The fix was released in v2.1.52, so simply updating to the latest version now resolves the issue. Windows error logs can be found at %APPDATA%\Code\logs.

Source: How to Fix Claude Code VS Code Extension Not Working — AIHackDeck

Claude Is Unresponsive or Freezes {#no-response}

You're signed in, the panel is open, but sending a prompt gets no response. Troubleshoot in this order:

1. Check your internet connection — Verify you have a stable connection
2. Start a new conversation — Open a different conversation and see if the problem persists
3. Check for detailed errors in the CLI — Running claude in the integrated terminal may reveal more detailed error messages

If a command hangs (freezes) during operation, first press Ctrl+C to cancel the current operation. If that doesn't respond, close the terminal and restart it. Your conversation is not lost — run claude --resume in the same directory to pick up where you left off.

If CPU and memory usage are high with a large codebase and performance feels slow, you can stabilize things by using /compact to periodically compress the context, closing and restarting Claude Code at task boundaries, and adding large build directories to .gitignore.

Source: Troubleshooting — Claude Code Docs / Using Claude Code in VS Code — Claude Code Docs

Terminal Says "IDE Not Detected" / Unstable Behavior in WSL {#ide-not-detected}

This covers cases where IDE integration doesn't work when using the CLI, or behavior is unstable in WSL. First, understand how integration works:

1. Launch from the integrated terminal — Running claude in VS Code's integrated terminal (Ctrl+` / Cmd+`) automatically integrates with the IDE, enabling diff display and diagnostic sharing
2. Use /ide for external terminals — If you launched Claude Code from a terminal outside VS Code, run /ide inside Claude Code to connect to VS Code
3. Launch with code . — If VS Code isn't in your PATH as the code command, integration won't work. Re-open by running code . from your terminal to inherit the environment

A WSL-specific issue: search results can come back incomplete. This is caused by the read penalty for crossing between Windows and Linux filesystems — searches work but some matches aren't returned (in this case, /doctor will still show Search as OK). Here's how to address it:

1. Be more specific with searches — Narrow the search scope by specifying directories or file types
2. Place your project on the Linux side — Storing your project under /home/ rather than /mnt/c/ improves performance
3. Consider native Windows — Running natively on Windows rather than through WSL is also an option

If @file mentions or custom skills can't find files, the bundled ripgrep may not be working. Install the OS-level ripgrep (e.g., sudo apt install ripgrep on Ubuntu, or winget install BurntSushi.ripgrep.MSVC on Windows), then set the environment variable USE_BUILTIN_RIPGREP=0 to resolve the issue.

Source: Troubleshooting — Claude Code Docs / Using Claude Code in VS Code — Claude Code Docs

Resetting and Checking Logs When Nothing Else Works {#reset-and-logs}

If nothing above has resolved the issue, move on to resetting settings and checking logs.

1. Delete extension data and reset — To reset all settings, run the following command and reopen VS Code. This will delete Claude Code's conversation history, settings, and extension data. Back up the folder beforehand if needed. rm -rf ~/.vscode/globalStorage/anthropic.claude-code
2. Check extension logs — Run "Claude Code: Show Logs" from the command palette to view debug logs including authentication errors and port conflicts (Windows system logs are at %APPDATA%\Code\logs)
3. Report the issue — Use the /feedback command inside Claude Code, or check and report known issues on GitHub Issues

The fastest troubleshooting path is: run /doctor first (or claude doctor if it won't launch) for a full diagnosis → go to the relevant section of this article based on your symptom. Most "not working" cases come down to one of: version compatibility, sign-in, a known bug, or IDE integration — working through them from the top will resolve the majority of issues.

Source: Using Claude Code in VS Code — Claude Code Docs / Troubleshooting — Claude Code Docs

Sources

• Using Claude Code in VS Code — Claude Code Docs (prerequisites, sign-in, fixing common issues)
• Troubleshooting — Claude Code Docs (/doctor diagnostics, WSL search, ripgrep)
• How to Fix Claude Code VS Code Extension Not Working — AIHackDeck (v2.1.51 bug and downgrade steps)