Getting started

Install OpenClaw, run onboarding, and chat with your AI assistant in about 5 minutes. By the end you will have a running Gateway, configured auth, and a working chat session.

What you need

• Node.js 22.22.3+, 24.15+, or 25.9+ (Node 26 is the recommended runtime)
• An existing Claude Code or Codex CLI login, or a provider API key — onboarding can reuse it

Check your Node version with node --version. Windows users: the native Windows Hub app is the easiest desktop path. The PowerShell installer and WSL2 Gateway paths are also supported. See Windows. Need to install Node? See Node setup.

Try it in one command

npx openclaw@latest

On a fresh install, choose Quick start after a one-line pointer to the security guide. That is the only onboarding prompt when usable AI access is already available: OpenClaw finds an existing Claude Code or Codex CLI login or API key, verifies it with a real completion, saves the config, and opens the web dashboard.

The Gateway runs in this terminal until you press Ctrl+C; your config stays saved. If no detected route works, onboarding opens manual provider setup. Choose Custom setup to walk through all guided options instead.

To keep the Gateway running in the background later, install the CLI below and run openclaw gateway install. Run openclaw for the TUI or openclaw dashboard to reopen the web UI.

Quick setup

1. Install OpenClaw

   macOS / Linux

   curl -fsSL https://openclaw.ai/install.sh | bash
   

   

   Windows (PowerShell)

   iwr -useb https://openclaw.ai/install.ps1 | iex
   

   Other install methods (Docker, Nix, npm): Install.

2. Complete onboarding

   The installer starts the onboarding wizard automatically. Choose Quick start to reuse detected AI access and open the dashboard, or Custom setup for the full guided flow. Provider sign-in and optional setup can take longer; return later with openclaw configure for additional settings. Quick start keeps the Gateway in the foreground. For background operation, stop it with Ctrl+C, then run openclaw gateway install.

   See Onboarding (CLI) for the full reference.

3. Verify the Gateway is running

   openclaw gateway status
   

   You should see the Gateway listening on port 18789.

4. Open the dashboard

   openclaw dashboard
   

   This opens the Control UI in your browser. If it loads, everything is working.

5. Send your first message

   Type a message in the Control UI chat and you should get an AI reply.

   Want to chat from your phone instead? The fastest channel to set up is Telegram (just a bot token). See Channels for all options.

Advanced: mount a custom Control UI build

If you maintain a localized or customized dashboard build, point gateway.controlUi.root to a directory that contains your built static assets and index.html.

mkdir -p "$HOME/.openclaw/control-ui-custom"
# Copy your built static files into that directory.

Then set:

{
  "gateway": {
    "controlUi": {
      "enabled": true,
      "root": "${HOME}/.openclaw/control-ui-custom"
    }
  }
}

Restart the gateway and reopen the dashboard:

openclaw gateway restart
openclaw dashboard

If setup does not work

One command turns the current state of your install into a diagnosis you can act on:

openclaw triage

It runs read-only health checks, writes a sanitized prompt describing what it found, and then offers to hand that prompt to a coding agent it detects on your machine — Claude Code, Codex CLI, or the built-in OpenClaw agent — so the agent starts with the diagnosis already loaded. Pick “just print the commands” if you would rather run the handoff yourself.

Nothing leaves your machine until you choose an agent, and secrets, tokens, raw chat payloads, and raw logs are excluded from the prompt.

To read the findings yourself instead, run openclaw doctor. For symptom-first routes, see Troubleshooting.

What to do next

Connect a channel

Discord, Feishu, iMessage, Matrix, Microsoft Teams, Signal, Slack, Telegram, WhatsApp, Zalo, and more.

Pairing and safety

Control who can message your agent.

Configure the Gateway

Models, tools, sandbox, and advanced settings.

Browse tools

Browser, exec, web search, skills, and plugins.

Advanced: environment variables

If you run OpenClaw as a service account or want custom paths:

• OPENCLAW_HOME — home directory for internal path resolution
• OPENCLAW_STATE_DIR — override the state directory
• OPENCLAW_CONFIG_PATH — override the config file path

Full reference: Environment variables.

Related

• Install overview
• Channels overview
• Setup
• Triage
• Troubleshooting