OpenClaw Docs Guide
Where the official OpenClaw docs live, what to read first, and how to navigate them without getting lost.
Where the official docs live
If you are looking for the canonical OpenClaw documentation, start here:
The official docs are broad and fast-moving. That is good for exact flags and current behavior, but it can be overwhelming if you just want “what should I read first?”
This page is the answer to that question.
Start here if you are new
If you want the shortest path from zero to a first working chat, read these in order:
That path matches the way the official repo is currently framed:
- install the CLI
- run
openclaw onboard --install-daemon - verify the Gateway
- open the dashboard
If you want the search-friendly version first, use this site as the entry layer:
Read these next if you operate the Gateway
Once the first install works, the most important official docs are operational:
This is the shift many people miss. OpenClaw is not just a chatbot with connectors. It is an always-on gateway and workspace system. The docs reflect that.
Read these if you are adding channels
Channel setup is a second phase, not the first one. Once the dashboard path works, then it makes sense to go deeper into messaging surfaces:
If you only want the easiest starter path, begin with:
If you are specifically deploying through Tencent Cloud Cloud Phone and want a China-native route, also see:
Read these if you care about models, tools, and memory
The official docs split these concerns more cleanly than most people expect:
On this site, the closest supporting pages are:
Read these if you use apps or nodes
OpenClaw’s official docs also cover the device-side story:
This matters because the Gateway is not the whole product. The official README is very clear on this point: the Gateway is the control plane, while the assistant lives across channels, tools, and device nodes.
The fastest reading order for most people
If you only want a practical docs sequence, use this:
- official
Getting Started - official
Onboarding Wizard - official
Gateway configuration - official
Security - official
Troubleshooting - only then the specific channel, browser, node, or skills page you need
That order saves time because it follows how OpenClaw actually works, not how people usually want to skip ahead.
This site vs the official docs
Use both, but use them for different jobs.
Use the official docs when you need:
- exact commands
- current config keys
- platform-specific runbooks
- canonical behavior for the latest release
Use this site when you need:
- plain-language explanations
- search-first landing pages
- decision help between two routes
- a faster answer to “what matters here?”
The combination is better than either one alone.
FAQ
Does the README replace the docs?
No. The README is a strong overview and launch point, but the full operational detail lives in the docs.
What should I read right after onboarding?
Read Gateway configuration, security, and troubleshooting before you expand into more channels or public exposure.
I only want the most important official page. Which one is it?
For first-time setup, it is Getting Started. For actual operations after that, it is usually Gateway configuration.
Is this site trying to mirror the official docs?
No. It is better used as a search-friendly guide layer that helps you reach the right official page faster.