Question 1

What is OpenClaw?

Accepted Answer

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.

Question 2

What's the essential difference from ChatGPT / Claude?

Accepted Answer

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.

Question 3

Does OpenClaw have its own LLM?

Accepted Answer

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.

Question 4

Is my data private with local models?

Accepted Answer

**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.

Question 5

Does it support DeepSeek API?

Accepted Answer

✅ 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.

Question 6

Does it support local DeepSeek (Ollama)?

Accepted Answer

✅ 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)**.

Question 7

What is the relationship between OpenClaw and Ollama?

Accepted Answer

**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.

Question 8

Do I need to know programming?

Accepted Answer

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.

Question 9

Can it run on Windows / Mac / Linux?

Accepted Answer

✅ 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.

Question 10

Can OpenClaw run continuously?

Accepted Answer

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.

Question 11

Why am I getting JSON parsing errors?

Accepted Answer

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)**.

Question 12

Is OpenClaw safe? How to prevent Prompt Injection?

Accepted Answer

**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)**.

Question 13

Will it 'go rogue'?

Accepted Answer

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'.

Question 14

Suitable for production?

Accepted Answer

**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.

Hardware Reality Check

Decision Tree

☁️ Cloud GPU (VPS)

Vultr High Frequency GPU

Other Options

💻 Local Hardware

Mac Mini (M4/M4 Pro, 16GB+)

NVIDIA GPU (4060 Ti 16GB+ or used 3090 24GB)

🔑 API Services

DeepSeek API

Not sure if your hardware can handle it?