OpenClaw Setup Checklist

OpenClaw Setup Checklist

This page exists to bridge the gap between "I ran the install" and "I know everything is working."

Use it after you finish the Installation Guide. Do not skip ahead to building workflows until every item below is green.

Phase 1: environment baseline

Before touching OpenClaw itself, confirm your machine is ready:

• Node.js 22 or newer is installed (node -v)
• pnpm is available (pnpm -v)
• You have a terminal that supports interactive sessions
• Your network can reach the model provider API you plan to use
• Docker is installed only if you actually need container workflows

If any of these fail, fix them first. OpenClaw setup will not fix broken baselines.

Phase 2: OpenClaw installation verified

Confirm the install itself completed cleanly:

• OpenClaw CLI or app is installed
• Running openclaw --version or opening the app shows a valid version number
• You have chosen one install lane (app-first or source-first) and stuck with it

Phase 3: workspace and config created

Your workspace is where OpenClaw stores everything local:

• Running setup created a workspace directory
• A config file exists in the workspace
• The config file contains your model provider credentials
• No obvious errors appeared during setup (auth failures, permission errors, missing files)

Where to find your workspace:

• default location: ~/.openclaw/
• config file: openclaw.json or equivalent
• workspace data: the workspace directory under ~/.openclaw/

If the workspace does not exist, re-run the setup flow from the Installation Guide.

Phase 4: Gateway is running

Gateway is the process that makes OpenClaw actually operate. Without it, nothing works:

• Gateway started without crashing
• The terminal shows Gateway is running (or the app reports "Gateway: active")
• No port conflicts or permission errors appeared in the startup logs

How to check:

• app-first users: the app dashboard usually shows Gateway status
• source-first users: run openclaw gateway status or check the terminal output

If Gateway will not start, the most common causes are:

• port already in use
• missing or invalid config
• wrong Node.js version

Phase 5: first channel connected

Pick one channel and connect it. Do not connect multiple channels yet:

• You chose one channel to start with (Discord, Telegram, etc.)
• Channel credentials were added to the config
• OpenClaw reports the channel as connected
• No authentication or permission errors appeared

Good first channel choices:

• Discord: easy to set up, easy to test, good visibility
• Telegram: simple bot API, quick verification
• CLI/test channel: lowest friction if you just want to verify the loop

Do not try to connect WeChat, Lark, or other complex channels on your first setup.

Phase 6: first real message loop

This is the only test that matters. If this works, everything else is secondary:

• You sent a real message to the assistant through the channel
• The assistant received it
• The assistant generated a reply
• The reply appeared back in the channel

If this loop works, your setup is good. If it does not:

• check Gateway logs for errors
• confirm channel credentials are correct
• verify model provider API key is valid and has credits
• make sure the message is reaching OpenClaw (not just sitting in the channel)

Phase 7: health check passed

Run a health check if your version supports it:

• openclaw doctor or equivalent health check command runs
• No critical issues are reported
• Model provider connectivity is confirmed
• Channel connectivity is confirmed

If the health check reports warnings but the message loop works, the warnings can wait. Fix critical issues only.

What to do after everything passes

Your setup is complete. Move to the next step in this exact order:

1. OpenClaw Discord Guide — set up one production channel with a real use case
2. OpenClaw Heartbeat Guide — add a recurring check so you know when something breaks
3. OpenClaw Use Cases — pick a workflow pattern and start building

Do not jump to use cases or skills until you have a healthy channel and at least one heartbeat running.

What to do if something fails

Go back to the Installation Guide and review the "Common failure points" section.

The most frequent issues are:

• wrong Node.js version
• Gateway not actually running
• channel linked but no reply (usually a provider or config issue)
• mixing app-first and source-first install steps

For additional resources, see the OpenClaw Resources page.

Next step

• Discord Guide
• Heartbeat Guide
• Use Cases
• Platforms
• Comparisons
• Resources