Free lesson

A clean OpenClaw lab

A clean OpenClaw lab — OpenClaw in a read-only lab. One trust boundary; Check current prerequisites; Install without Quick start. Practical assignment: Practice: A clean OpenClaw lab.

Demo edition. The materials are undergoing editorial review.

Topics covered

  • One trust boundary
  • Check current prerequisites
  • Install without Quick start

One trust boundary

This course builds a local reader of fictional notes inside a fresh Linux VM. Do not mount your main computer's home directory, SSH keys, browser profile, host Docker socket or working repository. Use a dedicated lab account without existing Claude/Codex logins or provider-key environment variables. The Gateway belongs to one trusted operator; it is not a hostile multi-tenant boundary. A tool sandbox adds a second layer inside the VM, while the Gateway process remains on that VM's host. Choose VM networking without public port forwarding. Internet access may be needed to download packages and a local model, but the task itself will use local services only. Produce a VM → Gateway → read-only workspace diagram. If production credentials or working folders are already visible in the VM, fix isolation before installing OpenClaw.

Check current prerequisites

At the research date, current documentation requires Node 24.16.0+ on the 24 branch or 26.1.0+, with patched 24.22.1+/26.12.1+ builds recommended. Recheck this version-sensitive requirement before your own installation. The tool sandbox needs Docker inside the VM. Record Node, npm and Docker versions in inventory.md. This exercise installs no Python on the Mac; learner commands belong inside the Linux VM and require no learner-written Python scripts. If Docker is unavailable, prepare files and review documentation, but do not disable sandboxing just to pass the exercise. Local-model weights, context and runtime all consume resources; download size does not equal the complete RAM requirement. The expected artifact is a verified inventory and an environment suitability decision. The author has not executed these commands on your computer.

node --version
npm --version
docker version

Install without Quick start

In the clean VM, install the CLI using the documented npm route. The allow-scripts option applies to npm12 or npm11.16+; official instructions omit it for older npm. Package lifecycle scripts execute code, which is why installation belongs inside the lab. Record the exact OpenClaw version, and use that reviewed version instead of latest when reproducing the environment. Do not run bare openclaw, npx openclaw@latest or onboard: the current Quick start can discover an existing login, verify it with a real completion and offer a background service. We will author configuration manually and keep the Gateway in the foreground. Expect an installed CLI with help available, without a model run, connected channel or daemon. If an installer opens onboarding, exit before selecting a provider and return to the manual path.

# npm 12 or npm 11.16+; only inside the isolated Linux VM.
npm install -g openclaw@latest --allow-scripts=openclaw
openclaw --version
openclaw --help

Practical assignment

Practice: A clean OpenClaw lab

Continue to learning

Course outline

  1. A clean OpenClaw lab
  2. Separate configuration and task data
  3. Read-only sandbox and tool policy
  4. Local model and first turn
  5. A custom skill without new permissions
  6. Controlled project and evidence