From Zero to AI Assistant in Under 5 Minutes: Setting Up OpenClaw

Published: April 2026

Most "personal AI" setups involve a Saturday afternoon, three broken installs, and a Stack Overflow tab you never closed.

OpenClaw is not that.

One command. A guided wizard. Done.

Here's what actually happens when you set it up — no fluff, no gotchas hidden in step 7.

What You Need Before You Start

• A Mac, Linux machine, or Windows PC (with WSL2)
• Node.js 22+ — but don't worry if you don't have it. The installer detects and handles it.
• An internet connection
• About 5 minutes

That's the whole prereq list.

Step 1: Run the Installer

Open your terminal and paste one line:

macOS / Linux / WSL2:

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

Windows (PowerShell):

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

The script does three things automatically:

1. Checks if Node 22+ is installed — installs it if not
2. Installs the OpenClaw CLI globally via npm
3. Launches the onboarding wizard

You don't touch any of that. It just happens.

Step 2: Follow the Onboarding Wizard

The wizard walks you through configuration in plain English. No YAML files. No JSON configs. No environment variable archaeology.

It asks you:

• What to call your assistant
• Which channel to connect (Telegram, WhatsApp, Discord, Signal — your pick)
• Basic preferences

Each step is a prompt-and-answer. If you're not sure about something, the defaults are sensible.

When it's done, the daemon installs itself and starts automatically.

Step 3: Verify It's Running

openclaw doctor    # checks for any config issues
openclaw status    # confirms the gateway is live
openclaw dashboard # opens the browser UI

If openclaw doctor comes back clean, you're fully operational.

What You Have Now

After those three steps, you have:

• A persistent AI assistant running as a background service on your machine — it starts automatically on boot
• A connected messaging channel — so you can reach your assistant from your phone via Telegram, Signal, or wherever you set up
• A browser dashboard at localhost for when you're at your desk
• A workspace where your assistant stores memory, files, and context across sessions

This isn't a chatbot you visit. It's something that lives with you and accumulates context over time.

Connecting Your First Channel (Takes 2 Minutes)

The most useful thing you can do immediately after setup: connect Telegram.

1. Open Telegram and search for @BotFather
2. Send /newbot and follow the prompts to get a bot token
3. Run openclaw channels login and paste the token when asked

That's it. Now you can message your assistant from your phone anywhere, and it has full access to everything you've configured on your machine.

If Telegram isn't your thing, the same flow works for Discord, WhatsApp, and Signal.

The Part Nobody Talks About: First-Day Personalization

Setup takes 5 minutes. Making it yours takes another 10, and it's worth doing.

Two files define how your assistant behaves:

SOUL.md — Your assistant's personality and rules. Open it and write how you want it to communicate. Formal or casual. When to ask before acting externally. What it should never do. Write it like you're onboarding a new hire.

USER.md — About you. Your name, your timezone, your current projects. The more context you give it here, the better it performs from day one instead of learning everything from scratch.

These are plain Markdown files in your workspace directory. Edit them in any text editor.

Troubleshooting: The One Thing That Trips People Up

If you type openclaw after install and get command not found, it's a PATH issue — the global npm bin directory isn't in your shell's PATH.

Quick fix:

export PATH="$(npm prefix -g)/bin:$PATH"

Add that to your ~/.zshrc or ~/.bashrc, then open a new terminal. Done.

Run openclaw doctor to confirm everything is wired up correctly.

What's Next

Once you're running, the natural next moves are:

• Set up a daily brief cron — have your assistant surface important items every morning without you asking
• Add your docs to the workspace — so your assistant has context about your work
• Try a first real delegation — ask it to research something, draft a message, or summarize a document

None of that requires additional setup. It's all available from the moment the wizard completes.

Why This Matters

Most tools claim to be easy to set up. OpenClaw actually is. One command handles the install, one wizard handles configuration, and five minutes later you have a persistent AI assistant connected to your life — not a web tab you have to remember to open.

The barrier to getting started is genuinely low. The ceiling on what you can do with it is genuinely high.

Start with the install. See for yourself.

OpenClaw is open source and self-hosted. You own your data. Get started at openclaw.ai