How to Complete First-Time OpenClaw Setup and Onboarding
OpenClaw onboarding is the real first-run setup: it configures auth, the workspace, the gateway, optional channels, and the daemon, then hands you off to the Control UI.
How to complete first-time OpenClaw setup and onboarding
The onboarding wizard is where OpenClaw becomes usable. It configures your auth, workspace, gateway mode, optional channels, and background service, then points you to the Control UI for the first real session.
Who this is for
- You already installed the
openclawCLI. - You want to finish the first-run setup correctly.
- You want the dashboard working before you add more advanced routing or automation.
What you need before you start
- An installed
openclawcommand. - A provider credential for the model you plan to use.
- A browser on the same machine or a secure path back to the gateway host.
Step-by-step setup
Step 1: Run the onboarding wizard
| openclaw onboard --install-daemon |
The official wizard docs describe this as the recommended way to configure a local or remote gateway, channels, skills, and workspace defaults in one guided flow.
Step 2: Choose the right onboarding mode
The wizard starts with QuickStart versus Advanced. If this is your first OpenClaw install, use QuickStart unless you already know you need a remote gateway, custom binding mode, or a non-default workspace.
Step 3: Configure web search if you skipped it in the wizard
| openclaw configure --section web |
Expected result: OpenClaw stores the search provider API key under the correct config path so the web_search tool can work later.
Step 4: Confirm the gateway is healthy
| openclaw gateway status |
Expected result: the gateway service is running and the probe succeeds.
Step 5: Open the dashboard
| openclaw dashboard --no-open |
Open the printed URL in your browser. The dashboard docs note that the first successful load stores the token locally in the browser.
Step 6: Approve the browser if the Control UI asks for pairing
| openclaw devices list |
| openclaw devices approve --latest |
Expected result: the pending device request is approved and the dashboard reconnects cleanly.
Verify it worked
- The dashboard loads.
openclaw gateway statusshows a healthy runtime.- You can open the settings panel in the Control UI without being disconnected.
Common problems and fixes
The wizard finished, but the dashboard shows unauthorized
Get a fresh URL from the CLI:
| openclaw dashboard --no-open |
Then use the printed URL and confirm the same gateway token is configured.
The dashboard shows disconnected (1008): pairing required
Approve the pending browser device:
| openclaw devices list |
| openclaw devices approve --latest |
I need to change part of the setup later
Use the reconfiguration command instead of reinstalling:
| openclaw configure |
FAQ
What does the wizard configure by default?
The official onboarding docs say it walks through model auth, workspace location, gateway settings, channels, daemon install, and a health check.
Do I need to finish channel setup before I can use the dashboard?
No. The dashboard is explicitly documented as the fastest first chat path and does not require a channel.
When do device approvals happen?
Local 127.0.0.1 dashboard access is auto-approved. Remote connections or different browser identities can require a one-time device approval.
Official sources
Related OpenClaw guides
Follow the next most relevant setup guide without leaving the cluster.
Build a conservative OpenClaw WhatsApp assistant with allowlists, group restrictions, and a dedicated number before enabling more automation.
Tune the OpenClaw workspace files, configure web tools, and enable a safer sandbox profile without guessing config paths.
Turn on OpenClaw heartbeats, keep them quiet outside active hours, and verify they run without spamming you.