10-minute first assistant onboarding

Build your first OpenClaw AI assistant in 10 minutes

The fastest path from zero to a working private assistant: pick where it runs, create a Telegram bot, run one install command, finish the wizard, then send the first message.

Open the full Day 2 setup guide →Start the 7-day path

✓ Native Windows supported

✓ QuickStart wizard

✓ Telegram first channel

✓ No platform lock-in

The 10-minute route

Choose where the assistant lives

Use native Windows for a quick trial, or a small Ubuntu cloud server for 24/7 availability. WSL2 is optional.

Step 1

Prepare model and Telegram access

Use a Claude subscription OAuth flow when available, or prepare an API key. Create a bot with @BotFather and keep the token private.

Step 2

Run one install command

The install script pulls dependencies and enters the interactive QuickStart wizard automatically.

Step 3

Send the first message

After Telegram admin setup, message your bot and verify that your assistant answers from your own runtime.

Step 4

Answer first: what do I need before starting?

A computer or small cloud server, one AI model login or API key, and a Telegram bot token. If you use Windows, OpenClaw can run on native Windows; WSL2 is optional, not required.

Install command

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

First-run checklist

0/5

Check all 5 items first, then click this button to avoid counting an incomplete install as done.

What counts as a verified first run?

Install copied

You copied the command and ran it in your own terminal.

Telegram replied

Your bot answered from the machine or server you control.

Errors have a next step

If the reply fails, check token, allowlist, model access, and terminal logs before reinstalling.

Do not paste secrets into public chats

Bot tokens and API keys should stay in your local terminal or server environment only. The tutorial masks all example tokens.

If the first reply fails

• Check the bot token and admin allowlist
• Confirm the model login/API key is still valid
• Restart OpenClaw and read the terminal error before reinstalling

Common first-run fixes

Most failed first replies come from one of four checks. Use this rail before reinstalling.

Bot token mismatch

Regenerate only if the token was pasted into the wrong runtime. Otherwise update the local config and restart.

Admin allowlist missing

Confirm your Telegram user ID is in the allowlist before testing from another account.

Model login expired

Run the provider auth/status command and refresh OAuth or API key only when it reports expired.

OpenClaw process stopped

Restart the process and check the latest terminal log before changing configuration.

Low-risk next step

After the first reply, choose one trackable action

No payment or public posting here. These course, community, and product-referral clicks are lead proxies so the next review can judge whether OpenClaw101 has real business handoff.

Want a guided setup?

Use the course path when you want a structured first assistant build instead of debugging alone.

View the OpenClaw course →

Need community help?

Join the community after you have a screenshot or log from your first-run attempt.

Open community →

Compare nearby tools

Browse Skill Hub CN when your next step is prompt packs, agent skills, or workflow templates.

Browse Skill Hub CN →