How to Fix OpenClaw Not Discoverable on Path After Installation

If you see the message “installed, but openclaw is not discoverable on path in this shell”, don’t panic. OpenClaw is usually installed correctly, but Windows cannot find the executable because the npm global directory is missing from your system PATH. That’s why the command fails even though the installer shows everything as OK.

This guide explains exactly why this happens and shows you how to fix the PATH issue on Windows step by step so you can run OpenClaw without reinstalling anything.

Why OpenClaw Installs but Does Not Run

OpenClaw installs through npm and places its executable in a global npm folder. On Windows, this folder is often not added to the system PATH automatically.

When the PATH variable does not include the npm global bin directory, PowerShell cannot locate the openclaw command—even though OpenClaw is installed correctly.

Step 1: Confirm the Issue

Open PowerShell and run:

where.exe openclaw

If PowerShell returns nothing, OpenClaw is not on PATH.

You can also verify Node.js is installed:

node -v

If Node.js works but openclaw does not, the problem is PATH-related.

Step 2: Temporarily Fix PATH (Quick Test)

Use this method to confirm the root cause.

Run this in PowerShell:

$env:Path = "C:\npm-global\bin;$env:Path"

Now test again:

where.exe openclaw
openclaw --version

If the command works, you have confirmed the issue.

This fix applies only to the current PowerShell session.

Step 3: Permanently Add OpenClaw to PATH (Recommended)

To avoid repeating the fix every time, add the npm global bin folder permanently.

Steps:

1. Press Win + R, type sysdm.cpl, and press Enter
2. Open the Advanced tab
3. Click Environment Variables
4. Under User variables, select Path → Edit
5. Click New and add:C:\npm-global\bin
6. Click OK on all windows
7. Close and reopen PowerShell

Now test:

openclaw --version

OpenClaw should run normally.

Step 4: Start OpenClaw Properly

OpenClaw does not launch automatically after installation. You must start its services manually.

Run the gateway:

openclaw gateway --port 18789

Keep this terminal open.

Open a new terminal and launch the dashboard:

openclaw dashboard

This starts the OpenClaw interface.

Common Mistakes to Avoid

• Reinstalling OpenClaw repeatedly (not needed)
• Reinstalling Node.js (already detected)
• Running commands from C:\Windows\System32 without fixing PATH
• Assuming “won’t run” means a failed installation

If OpenClaw installs successfully but does not run on Windows, the installation is not broken.
The issue happens because Windows cannot locate the executable in PATH.

Adding the npm global bin directory to PATH fixes both:

• “OpenClaw installed but won’t run”
• “OpenClaw is not discoverable on path in this shell”

Once PATH is set correctly, OpenClaw works as expected.