You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Claude Code is installed from [NPM](https://www.npmjs.com/package/@anthropic-ai/claude-code). Claude Code runs locally. In order to interact with the LLM, Claude Code sends data over the network. This data includes all user prompts and model outputs. The data is encrypted in transit via TLS and is not encrypted at rest. Claude Code is compatible with most popular VPNs and LLM proxies.
Copy file name to clipboardExpand all lines: docs/troubleshooting.md
+54Lines changed: 54 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,44 @@ You might encounter the following issues in WSL:
15
15
16
16
**Node not found errors**: If you see `exec: node: not found` when running `claude`, your WSL environment may be using a Windows installation of Node.js. You can confirm this with `which npm` and `which node`, which should point to Linux paths starting with `/usr/` rather than `/mnt/c/`. To fix this, try installing Node via your Linux distribution's package manager or via [`nvm`](https://github.com/nvm-sh/nvm).
17
17
18
+
**nvm version conflicts**: If you have nvm installed in both WSL and Windows, you may experience version conflicts when switching Node versions in WSL. This happens because WSL imports the Windows PATH by default, causing Windows nvm/npm to take priority over the WSL installation.
19
+
20
+
You can identify this issue by:
21
+
22
+
* Running `which npm` and `which node` - if they point to Windows paths (starting with `/mnt/c/`), Windows versions are being used
23
+
* Experiencing broken functionality after switching Node versions with nvm in WSL
24
+
25
+
To resolve this issue, fix your Linux PATH to ensure the Linux node/npm versions take priority:
26
+
27
+
**Primary solution: Ensure nvm is properly loaded in your shell**
28
+
29
+
The most common cause is that nvm isn't loaded in non-interactive shells. Add the following to your shell configuration file (`~/.bashrc`, `~/.zshrc`, etc.):
Avoid disabling Windows PATH importing (`appendWindowsPath = false`) as this breaks the ability to easily call Windows executables from WSL. Similarly, avoid uninstalling Node.js from Windows if you use it for Windows development.
54
+
</Warning>
55
+
18
56
### Linux and Mac installation issues: permission or command not found errors
19
57
20
58
When installing Claude Code with npm, `PATH` problems may prevent access to `claude`.
@@ -169,6 +207,22 @@ pacman -S ripgrep
169
207
170
208
Then set `USE_BUILTIN_RIPGREP=0` in your [environment](/en/docs/claude-code/settings#environment-variables).
171
209
210
+
### Slow or incomplete search results on WSL
211
+
212
+
Disk read performance penalties when [working across file systems on WSL](https://learn.microsoft.com/en-us/windows/wsl/filesystems) may result in fewer-than-expected matches (but not a complete lack of search functionality) when using Claude Code on WSL.
213
+
214
+
<Note>
215
+
`/doctor` will show Search as OK in this case.
216
+
</Note>
217
+
218
+
**Solutions:**
219
+
220
+
1.**Submit more specific searches**: Reduce the number of files searched by specifying directories or file types: "Search for JWT validation logic in the auth-service package" or "Find use of md5 hash in JS files".
221
+
222
+
2.**Move project to Linux filesystem**: If possible, ensure your project is located on the Linux filesystem (`/home/`) rather than the Windows filesystem (`/mnt/c/`).
223
+
224
+
3.**Use native Windows instead**: Consider running Claude Code natively on Windows instead of through WSL, for better file system performance.
225
+
172
226
## Markdown formatting issues
173
227
174
228
Claude Code sometimes generates markdown files with missing language tags on code fences, which can affect syntax highlighting and readability in GitHub, editors, and documentation tools.
0 commit comments