github/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-04-19 07:07:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(install): correct Windows PATH troubleshooting docs (#28102)

Browse Source 
* fix(install): correct Windows PATH troubleshooting — no \bin suffix needed (closes #19921)

* fix(docs): apply same PATH fix to FAQ
This commit is contained in:
Glucksberg
2026-03-02 13:07:07 -04:00
committed by GitHub
parent 11562c452a
commit 7a55a3ca07
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/help/faq.md
View File

@@ -578,7 +578,7 @@ Two common Windows issues:
npm config get prefix npm config get prefix
``` ```
- Ensure `<prefix>\\bin` is on PATH (on most systems it is `%AppData%\\npm`). - Add that directory to your user PATH (no `\bin` suffix needed on Windows; on most systems it is `%AppData%\npm`).
- Close and reopen PowerShell after updating PATH. - Close and reopen PowerShell after updating PATH.
If you want the smoothest Windows setup, use **WSL2** instead of native Windows. If you want the smoothest Windows setup, use **WSL2** instead of native Windows.

2
docs/install/installer.md
View File

@@ -384,7 +384,7 @@ Use non-interactive flags/env vars for predictable runs.
</Accordion> </Accordion>
<Accordion title='Windows: "openclaw is not recognized"'> <Accordion title='Windows: "openclaw is not recognized"'>
Run `npm config get prefix`, append `\bin`, add that directory to user PATH, then reopen PowerShell. Run `npm config get prefix` and add that directory to your user PATH (no `\bin` suffix needed on Windows), then reopen PowerShell.
</Accordion> </Accordion>
<Accordion title="Windows: how to get verbose installer output"> <Accordion title="Windows: how to get verbose installer output">