Why this lesson matters
This is the lesson that sets your tone for the whole tool. If installation feels vague, everything after it feels fragile. If installation feels controlled and verifiable, learners trust the rest of the course.
Installation and first-run success
Lesson 1: Install OpenClaw and reach the first working chat
A plain-language walkthrough of the official getting-started flow, from prerequisites to the first dashboard session.
People who need a confidence-building first win before they can trust the rest of the tool.
Learning goals
- Understand the official baseline before touching any advanced customization
- Separate installation from onboarding so the workflow makes sense
- Verify success using visible system checks instead of intuition
Prerequisites
- A machine running macOS, Linux, or WSL2
- Node.js 22+ available locally
- Permission to install CLI tooling and open the local Control UI
How to use this lesson
Start with the key ideas, work through the action steps, then use the mistakes, notes, and assignment to turn the lesson into a repeatable habit.
Action steps
Step 1: Confirm the environment before installing
Check that the machine matches the officially supported baseline and that Node.js is current enough. This removes the most common hidden reason a beginner gets stuck before the tool even starts.
Frame this as a business habit: verify prerequisites first so later debugging stays focused on real workflow issues rather than environment drift.
Step 2: Use the standard installer instead of inventing a custom path
The official docs push learners toward the website installer because it gets them to a known-good baseline quickly. That is the right default for a first course experience.
Only after the learner has reached a successful first run should you discuss deeper customization.
Step 3: Run onboarding and let it wire together the usable environment
Onboarding is where the gateway, auth, and optional channels become a functioning system. Many beginners mentally collapse installation and onboarding into one step, but the docs clearly separate them.
Teaching that separation early makes later troubleshooting much easier because learners know which layer failed.
Step 4: Verify the gateway and open the local dashboard
A working local dashboard or Control UI is your first real proof that the setup succeeded. That is stronger than assuming success because the installer finished.
This verification moment should be treated as the first visible win in the lesson.
Start with the supported baseline
The official docs set a simple baseline: use Node 22 or newer, and prefer the standard installer instead of inventing a custom setup on day one. That matters because the first goal is not deep customization. The first goal is getting to a known-good environment quickly.
For macOS, Linux, or WSL2, the recommended path is the website installer. After that, the onboarding wizard can configure the gateway and guide you through the first interactive setup without requiring you to memorize the internals immediately.
Treat onboarding as the real first milestone
Many beginners stop after installing the CLI and think they are done. The official flow makes it clear that onboarding is what actually wires together auth, gateway settings, and optional channels.
For a course audience, the operational lesson is simple: installation only places the tool on the machine. Onboarding is what turns that installation into a usable working environment.
Verify with the dashboard, not with guesswork
The fastest confirmation path in the docs is to check the gateway and then open the dashboard or Control UI. If the local dashboard opens and you can interact with it, the setup is working at the level that matters for future lessons.
That is also the right business-building habit to teach: verify each layer with a visible success condition before you move to more advanced automation.
Common mistakes
- Treating installation output as proof that the full environment is ready
- Skipping onboarding and then assuming broken auth or gateway behavior is random
- Trying to customize configuration too early before the first working session exists
Practical notes
This lesson should feel calm and confidence-building, because setup anxiety is one of the biggest blockers for technical learning.
A business-friendly framing is that the first objective is operational clarity, not advanced power.
Assignment
Assignment: produce your first clean setup checkpoint
- Write down your machine baseline and Node version
- Complete the standard install path and onboarding flow
- Capture one concrete success signal, such as the local dashboard opening correctly
- Write one sentence describing what part of the stack you now believe is working
Key takeaway
A reliable OpenClaw setup is not just a CLI install. It is a verified environment with a known-good gateway and a visible first interaction.
Official sources
In this course
Related guides
Read the related guide and course overview if you want broader context around safety, workflow design, and the rest of the learning path.
Previous lesson
This is the first lesson in the path.
Next lesson
Lesson 2: Understand the Gateway, Control UI, and workspace strategy
What the Gateway does, how the Control UI connects, and why customization should live outside the main repo.
Continue to next lesson