Not an App. OpenClaw is an open-source AI Agent framework / execution AI assistant that runs on your computer or server to execute real tasks, not chat. **Real Talk:** It's basically a junior engineer with sudo privileges.

What's the essential difference from ChatGPT / Claude?

In short: ChatGPT 'thinks', OpenClaw 'does'. ChatGPT: Answers questions, gives advice OpenClaw: Reads files, runs commands, modifies code, executes workflows **Real Talk:** ChatGPT is a consultant. OpenClaw is an intern who actually does the work.

Does OpenClaw have its own LLM?

No. It's a 'scheduler' that needs you to connect: OpenAI, Claude or local models. 👉 It doesn't sell models, just makes models 'work'. **Real Talk:** You're the DJ. OpenClaw is just the mixer.

Is my data private with local models?

**Short answer:** If you use Ollama locally, yes. The model runs on your machine. **How to verify:** Don't take my word for it. Block outbound traffic (except localhost) via Little Snitch or `ufw`. If OpenClaw still talks to your local Ollama, it's local. If it hangs, check your `base_url`. **Caveat:** If you use API providers (DeepSeek, OpenAI, Anthropic), your prompts go to their servers. Read their privacy policies.

Does it support DeepSeek API?

✅ Yes. Set `LLM_PROVIDER=openai` and `BASE_URL=https://api.deepseek.com`. **Config example (.env)**: ```bash LLM_PROVIDER="openai" LLM_BASE_URL="https://api.deepseek.com" LLM_API_KEY="sk-your-key-here" LLM_MODEL="deepseek-reasoner" ``` 👉 See our **[DeepSeek Config Guide](/guides/how-to-use-deepseek-with-openclaw)** for full setup.

Does it support local DeepSeek (Ollama)?

✅ Yes. Use `provider: ollama`. **Config example (.env)**: ```bash # Install Ollama & pull model curl -fsSL https://ollama.com/install.sh | sh ollama run deepseek-r1:8b # Configure OpenClaw LLM_PROVIDER="ollama" LLM_BASE_URL="http://localhost:11434/v1" LLM_MODEL="deepseek-r1:8b" ``` ⚠️ **Warning:** Requires heavy hardware. See **[Hardware Reality Check](/guides/fix-openclaw-cuda-oom-errors)**.

What is the relationship between OpenClaw and Ollama?

**Ollama is the engine; OpenClaw is the driver.** Ollama runs the DeepSeek model (loads it into VRAM, handles inference). OpenClaw tells it what to do (reads files, runs commands, executes workflows). If Ollama is down, OpenClaw is useless. If OpenClaw isn't running, Ollama is just a chatbot. **Analogy:** Ollama = Engine, OpenClaw = Driver. You need both to drive the car.

Do I need to know programming?

Basic use: No coding needed, but need basic logic Advanced use: Knowing some command line/project structure helps 👉 It's not 'zero barrier', but 'low barrier, high ceiling'. **Real Talk:** If you don't know what `chmod +x` means, you're going to have a bad time.

Can it run on Windows / Mac / Linux?

✅ Mac: Most friendly ✅ Linux / Server: First choice for production ⚠️ Windows: Usually via WSL2 (strongly recommended) **Symptom:** `Error: connect ECONNREFUSED 127.0.0.1:11434` (Networking issue) **Real Talk:** Mac users suffer slowly (3.2 tokens/sec). Windows users suffer dramatically (WSL2 drama). Linux users just suffer.

Can OpenClaw run continuously?

Yes. It can: run long-term, retry on failure, save intermediate state, stop by rules. This is why it's called an autonomous agent. **Real Talk:** That's also why it's called a 'security risk'. It doesn't know when to quit.

Why am I getting JSON parsing errors?

DeepSeek R1 wraps responses in `` tags before the actual JSON. OpenClaw's JSON parser fails. **Symptom:** `SyntaxError: Unexpected token <` (The model is 'thinking' out loud) 👉 **Fix it here:** **[JSON Parsing Fix](/guides/fix-openclaw-json-mode-errors)**.

Is OpenClaw safe? How to prevent Prompt Injection?

**Think of OpenClaw as a junior engineer with sudo privileges.** If you wouldn't trust a junior intern with root access to this folder, don't trust the agent. **Real incidents I've stopped:** - Agent tried to `rm -rf .` to "clean build artifacts" - Agent attempted `curl unknown.sh | bash` because it needed a tool **Mitigation**: - Run in Docker container with read-only filesystem - Use dedicated device (Mac Mini, cheap server) - Block dangerous commands (rm, format, dd, etc.) - Review EVERY execution log 👉 **Read the full autopsy:** **[CVE-2026-25253 Analysis](/guides/openclaw-security-rce-cve-2026-25253)**.

If you give too many permissions, yes. OpenClaw's capabilities ≈ permissions you give Correct approach: read-only by default, specify writable directories, block dangerous commands **Real Talk:** 'Going rogue' is just a fancy way of saying 'it did exactly what you told it to do, not what you meant'.

Suitable for production?

**Short answer:** Yes. **Honest answer:** Only if you have strict guardrails. Otherwise, expect to wake up at 3 AM. **Production requirements**: - You know exactly what the agent can and cannot do - You have tested EVERY workflow in staging - You have permission isolation (read-only by default) - You have logging AND rollback mechanisms - You have a human reviewing every action If you're missing any of these, you're not ready for production. 👉 Beginners should NOT start with production.

Fix "spawn npm ENOENT" on Windows

Error Confirmation

Error: spawn npm ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)

Scope: This error occurs when OpenClaw attempts to install plugins on Windows. The child process spawn fails because Windows cannot locate npm.exe.

Error Code: ENOENT = "Error NO ENTry" — the Windows process loader searched the current directory, system directories, and PATH, but did not find the executable.

Verified Environment

Component	Version	Last Verified
Operating System	Windows 10/11	2026-02-04
Node.js	18.x LTS, 20.x LTS	2026-02-04
OpenClaw	Latest stable	2026-02-04
Shell	PowerShell 7+, CMD	2026-02-04

Note: This issue is specific to Windows process spawning behavior. Linux/macOS do not exhibit this failure mode.

3-Minute Sanity Check

Run these commands in the same terminal where you launch OpenClaw:

# 1. Is Node installed?
node --version
# Expected: v18.x.x or v20.x.x

# 2. Is npm accessible in THIS shell?
npm --version
# Expected: A version number

# 3. Where does Windows think npm is?
where npm
# Expected: A path like C:\Program Files\nodejs\npm.cmd

# 4. Is Node.js in your PATH?
$env:PATH -split ';' | Select-String nodejs
# Expected: At least one match

If any of these fail: Do not proceed. Your environment is missing Node.js or npm is not in PATH. Install Node.js LTS from nodejs.org first.

Decision Gate

Stop fighting VRAM physics.

Should you keep fixing this locally?

Continue local debugging only if:

You can reinstall Node.js without breaking other projects

You are allowed to modify system PATH and PowerShell policy

You have not already spent more than ~1 hour on this issue

Stop here if any apply:

You already reinstalled Node once and the error persists

This is a locked-down corporate Windows machine

You are debugging PATH / npm resolution for more than an hour

Past this point, debugging cost usually grows faster than results.

Primary Exit Path: WSL2

Install Windows Subsystem for Linux and run OpenClaw in a native Linux environment.

Why this works:

Linux has consistent PATH inheritance between shell and subprocess
No .cmd wrapper issues
Node.js behavior matches upstream expectations

Time investment: 20-30 minutes

Steps:

# 1. Install WSL2
wsl --install

# 2. Reboot when prompted

# 3. In WSL2 terminal, install Node.js 20 LTS
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
source ~/.bashrc
nvm install 20
nvm use 20

# 4. Install OpenClaw in WSL2
# (Follow standard Linux instructions)

Verification:

# In WSL2 terminal
node --version  # Should show v20.x.x
npm --version
which npm       # Should show /home/.../.nvm/versions/node/...

Secondary Exit Path (Conditional)

Use a remote Linux environment when:

WSL2 is blocked by organizational policy
You need GPU resources beyond what local hardware provides
You want to avoid any local environment modifications

Solution: Remote Linux VPS

Deploy to a cloud provider and access via SSH. This eliminates Windows-specific environment issues entirely.

Time investment: 15-20 minutes

Steps:

# 1. Provision a Linux VPS (Ubuntu 22.04 recommended)

# 2. SSH into the server
ssh user@your-server-ip

# 3. Install Node.js 20 LTS
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
source ~/.bashrc
nvm install 20
nvm use 20

# 4. Install OpenClaw
npm install -g @m1heng/openclaw

Why NOT Other Options

Option	Rejection Reason
Modify PATH manually	Does not persist for subprocess environments; IDEs and terminals inject different PATHs
Use nvm-windows	Adds another layer of PATH indirection; introduces race conditions with system installers
Reinstall Node.js	The installer correctly adds to PATH, but subprocess environments are sanitized by Windows
Switch to PowerShell 7	Does not solve the subprocess environment inheritance issue
Copy npm.cmd to System32	Fragile; breaks when Node updates; bypasses package manager entirely
Use `npm.cmd` explicitly	Requires modifying OpenClaw source code; not maintainable

Last Resort: Native Windows Debugging

Warning: This section is provided for documentation purposes only. If you have exhausted WSL2 and remote options and must use native Windows, proceed with caution.

Prerequisite: Only attempt this if:

Your organization prohibits WSL2 and external environments
You have explicit approval to modify system-level configurations

Step 1: Confirm Node.js LTS

node --version

If you see v21, v22, or v24: uninstall and install LTS from nodejs.org.

Step 2: Add Node.js to System PATH

Press Win + R, type sysdm.cpl, Enter
Advanced tab → Environment Variables
Under System variables (not User variables), find Path
Click Edit → New
Add: C:\Program Files\nodejs
Click OK on all dialogs
Restart your terminal completely

Step 3: Verify subprocess environment

# Open a FRESH PowerShell (not the one you were using)
node -e "console.log(process.env.PATH.split(';').find(p => p.includes('nodejs')))"

If this returns undefined, the PATH change did not propagate. Reboot your machine.

Step 4: Re-run OpenClaw installer

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\install.ps1

Summary

Check	Command	Pass Criteria
Node version	`node --version`	v18.x or v20.x
npm in shell	`npm --version`	Returns version
npm on disk	`where npm`	Returns path
npm in subprocess	`node -e "console.log(process.env.PATH)"`	Contains nodejs path

Decision:

All pass: Your environment is correct. The issue may be OpenClaw-specific. Report the bug with your diagnostic output.
Any fail: Use WSL2 or consult your system administrator.

Last resort: If you have spent more than 1 hour on this, stop debugging Windows internals. Use WSL2 or a remote Linux environment. The expected time investment for WSL2 is 20 minutes; continued debugging has unbounded time cost.

Fix 'Failed to start CLI: Error: spawn npm ENOENT' on Windows