← Back to Getting Started
OpenClaw getting started

Everyday commands that matter

Use this guide when you want the smallest command set that helps you finish setup, verify health, open the main interface, and handle basic troubleshooting.

First-week command layer Setup, verify, use the dashboard, then debug with evidence only when something feels wrong.
The six commands that matter first

Learn the smallest useful set

Setup

openclaw onboard --install-daemon

Use the guided setup flow for auth, gateway, and the first working baseline.

Health check

openclaw gateway status

Confirm the gateway is actually up before deeper debugging.

Snapshot

openclaw status

Get a broader operational snapshot when you need more than gateway up/down state.

Use the thing

openclaw dashboard

Open the normal Control UI and verify the system feels real.

Evidence

openclaw logs --follow

Use runtime evidence when something looks wrong or degraded.

Guided repair

openclaw doctor

Run health checks and guided repair suggestions when setup or health feels broken.

Best first sequence

Start simple

openclaw onboard --install-daemon
openclaw gateway status
openclaw dashboard

If something feels wrong after that, escalate to:

openclaw status
openclaw logs --follow
openclaw doctor
Simple mental model

Teach the commands in layers

  1. Setup: openclaw onboard --install-daemon
  2. Verify: openclaw gateway status and openclaw status
  3. Use it: openclaw dashboard
  4. Debug with evidence: openclaw logs and openclaw doctor
Where to go next

Continue the newcomer path