Pebellslearn by building
0%
RoadmapsMatrixCoursesSandboxSign in
Installing and Onboarding  ›  Lesson

Installing OpenClaw

Installation 11 minCheck that Node.js is recent enough, install the openclaw command globally with npm, then run the onboarding wizard, or run it inside a Docker container for isolation.

Installing OpenClaw

Once you have chosen a machine, installing OpenClaw takes about five minutes. What slows people down is rarely the install itself; it is doing the steps in the wrong order, or skipping the check that would have caught the problem.

The rule

Node first, then npm install, then onboard.

You need three things before you start: a recent version of Node.js, credentials for your model provider (usually an API key), and a terminal on the machine where the Gateway will run.

# 1. Check that Node.js is installed and recent enough
node --version

# 2. Install the openclaw command globally
npm install -g openclaw@latest

# 3. Start the guided setup
openclaw onboard
  • -g installs the package globally, so the openclaw command works from any folder, not just one project.
  • @latest asks npm for the newest published release.
  • The Node.js version OpenClaw requires can change between releases. Check the official docs for the current requirement rather than trusting an old tutorial.

Updating later is the same command again: npm install -g openclaw@latest fetches the newest release. Do it regularly, because many security fixes arrive in small patch releases.

Docker: the isolated install. Instead of installing onto the machine directly, you can run OpenClaw inside a Docker container, an isolated environment with its own filesystem and software. The install stays clean, it cannot clash with other programs on the machine, and removing or updating it means swapping the container. It also fits the security checklist: inside a container, the agent can reach only what you choose to share with it.

The shortcut

Each step proves the one before it. Do not move on until the current step has shown you it worked.

A clean install on a new serverStep 1 of 4
  1. Check Node

    node --version prints a version number. Compare it with the docs' requirement and upgrade first if it is older.

The trap is skipping the Node check. An outdated Node.js can fail in confusing ways during the install or on first run, and the error rarely says "your Node is too old".

Drills

Answer fast — trust the rule.

quick drill

What does -g do in npm install -g openclaw@latest?

quick drill

Where should you check which Node.js version OpenClaw needs?

quick drill

What comes right after a successful install?

quick drill

After installing, your shell says openclaw: command not found. What is the likely cause?

quick drill

What is a benefit of installing OpenClaw with Docker?

Remember

  • Node first, then npm install, then onboard.
  • Each step proves the one before: node --version, then openclaw --help.
  • Docker gives an isolated install; always check the Node requirement in the current docs.

Practice — level up

0/1 solved

Write your answer, then compare it with a rubric and a model answer.

ExplainInstall in the right order

Write the steps you would follow to install OpenClaw on a fresh server, explaining why each step comes where it does. Then explain why someone might choose a Docker install instead.