[DOCS] Inaccurate verification command in JetBrains troubleshooting for non-NPM installs

Resolved 💬 4 comments Opened Jan 19, 2026 by coygeek Closed Feb 27, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/jetbrains#command-not-found (Also located in docs/en/troubleshooting.md under IDE integration issues)

Section/Topic

IDE integration issues > Command Not Found

Current Documentation

Under the troubleshooting steps for "Command Not Found", step 1 currently reads:

1. Verify Claude Code is installed: npm list -g @anthropic-ai/claude-code

What's Wrong or Missing?

The current instruction assumes the user installed Claude Code via NPM. However, the documentation now promotes the Native installer (curl ... | bash), Homebrew, or WinGet as the recommended installation methods.

For users who installed via these recommended methods, running npm list -g @anthropic-ai/claude-code will return empty results or an error. This creates confusion, leading users to believe Claude Code is not installed when it actually is.

Suggested Improvement

Update the verification step to use a universal command check that works regardless of the installation method.

Suggested text:

1. Verify Claude Code is installed by checking the version: ``bash claude --version ` Or verify the executable path: * **macOS/Linux:** which claude * **Windows (PowerShell):** Get-Command claude`

Impact

High - Prevents users from using a feature

Additional Context

Since the npm installation method is marked as "deprecated" in setup.md, troubleshooting steps should prioritize commands compatible with the native binary installation.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗