claude-code - 💡(How to fix) Fix Spurious ~/.local/bin PATH warning on Windows [1 comments, 2 participants]

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…
GitHub stats
anthropics/claude-code#54697Fetched 2026-04-30 06:38:31
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

Bug description

On Windows, Claude Code displays the warning:

Native installation exists but C:\Users<user>.local\bin is not in your PATH.

The directory ~/.local/bin does not exist and nothing was installed there. The actual installation is at ~/.config/devai/bin/claude.exe. The warning appears to be checking for a Linux/Unix-convention path that is not relevant on Windows.

Expected behavior

This warning should not appear on Windows, or at minimum should only fire if the directory actually exists and contains a Claude binary.

Environment

  • OS: Windows 11 Enterprise 10.0.26100
  • Shell: Git Bash
  • Actual install location: C:\Users\<user>\.config\devai\bin\claude.exe
  • Warned path: C:\Users\<user>\.local\bin (does not exist)

extent analysis

TL;DR

The warning can be resolved by modifying the path check to account for the Windows installation location.

Guidance

  • The issue arises from a Linux/Unix-convention path being checked on a Windows system, where the actual installation is at ~/.config/devai/bin/claude.exe.
  • To mitigate this, the code should be updated to check for the correct Windows path instead of ~/.local/bin.
  • The warning should only be triggered if the directory exists and contains a Claude binary, to prevent false positives.
  • Consider adding an OS-specific check to handle the different installation paths on Windows and Linux/Unix systems.

Example

No code snippet is provided as the issue does not include the relevant code.

Notes

The solution may require modifications to the Claude Code installation or warning logic, and may involve adding OS-specific checks to handle different installation paths.

Recommendation

Apply a workaround by modifying the path check to account for the Windows installation location, as upgrading to a fixed version is not mentioned in the issue.

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…

FAQ

Expected behavior

This warning should not appear on Windows, or at minimum should only fire if the directory actually exists and contains a Claude binary.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Spurious ~/.local/bin PATH warning on Windows [1 comments, 2 participants]