A map of the OpenClaw docs

The OpenClaw documentation is large, generated in part, and reorganised often: many single pages have become indexes pointing at child pages, and every old anchor still resolves. That is good engineering and hard reading. Here is the map as the docs’ own front page draws it, with the pages we found ourselves returning to, so you can go to the right chapter first.

The chapters

• Get started and Install: the five-minute path, onboarding, every install method, and the platform pages for macOS, Windows and Linux.
• Channels: one page per chat app, each split into setup, access control, messaging behaviour and troubleshooting.
• Agents and Capabilities: architecture, multi-agent routing, memory, skills, the browser, exec approvals, and the concepts pages behind them.
• ClawHub and Models: the registry, and one provider page per model backend, local ones included.
• Gateway and Ops: configuration, remote access, sandboxing, automations, security, and the troubleshooting ladder.
• Reference and Help: the CLI, one page per command, releases, and the help section with the triage command.

Two conventions make the docs navigable. Each page opens with a summary and a read-when list, so you can tell in two lines whether it is the page you need. And the docs ship a generated docs map, a heading index of every page, built for agents reading the docs and just as useful for people.

This file is generated from docs/**/*.md and docs/**/*.mdx headings to help agents navigate the documentation tree.

The pages worth reading first

• Getting started, then the troubleshooting page, before anything else: the first tells you the happy path, the second what the path looks like when it is not.
• The security index and the hardened baseline, before you connect a channel that strangers can reach.
• The heartbeat and automations pages, before the first bill.
• The memory concept page, when the assistant forgets or repeats.

Our own guides follow the same order and quote those pages: OpenClaw setup, step by step is the five-minute path with the traps marked, and OpenClaw not responding is the troubleshooting ladder in plain language.

What the docs do not contain

A memory figure for the machine, a monthly bill, and an opinion about whether you should run it yourself. OpenClaw system requirements and What OpenClaw costs are our attempts at the first two; the third is the question the whole hosting industry exists to answer.

The docs and this blog

Every guide on this blog names the upstream page it was grounded in, because the docs are the source of truth and they move. When they move again, the guide will be wrong before the page is. Start at What is OpenClaw if you are new, and at Hosted OpenClaw on Diali if you have decided not to be the operator.

• Twelve chapters; get-started, channels, gateway and help are the four you will live in.
• Every page has a summary and a read-when line.
• The docs move; our guides say which page they came from.