Guides·Guide

How to install OpenClaw

Get OpenClaw running on your own machine, then understand what changes when you need it in production.

TL;DR

You can install OpenClaw on your own machine in a few minutes: meet the prerequisites, get the project, add a model provider key, connect a channel, and run it.

  • That is perfect for one agent.
  • Running it reliably for many agents in production is a different setup.
  • That is where managed hosting comes in.

Before you start: prerequisites

OpenClaw runs on your own hardware, so you need a machine and a few accounts.

  • A machine to run it on: your laptop, a Mac mini, a VPS or a server.
  • A model provider API key (your choice of LLM provider), or a local model.
  • At least one channel to talk to the agent, such as a chat app.
  • The runtime and tooling the project requires, per the official OpenClaw docs.

Install OpenClaw

The high-level flow is the same on any machine. Follow the official instructions for the exact commands.

  • Get OpenClaw from its official source, the project repository.
  • Install its dependencies following the official instructions.
  • Create your configuration: where state lives, which channels and skills are enabled.
  • Pin your version so an update does not change behavior unexpectedly.

Configure your model and channels

OpenClaw is model-agnostic, so you choose your provider.

  • Add your model provider key, or point it at a local model.
  • Connect a channel so you can send goals and get results back.
  • Enable the skills and integrations the agent needs for its job.
  • Store credentials carefully: they give the agent real access.

Run your first agent

Start OpenClaw, send it a goal from your channel, and watch it work: it reasons, calls the skills you enabled, and reports back. For a single personal agent on your own machine, you are done.

From a local install to production

Installing one OpenClaw is the easy part. The hard part starts when it has to run unattended, recover when it crashes, survive version updates, and scale to many agents without you babysitting each one. At that point you are operating infrastructure, not running an app.

A managed runtime removes that work: provisioning in seconds, automatic recovery, a versioned filesystem, integrations ready on day one, and safe density so many agents share capacity without crashing. Molted runs OpenClaw this way, so you skip the production setup entirely.

One agent

online

Easy to babysit.

A fleet, by hand

onlinecrashedout of memoryconfig broken
Every red, amber or grey square is a silent outage: an agent down until someone notices. One is manageable. Hundreds, each failing in its own way around the clock, is impossible without watchers and automatic recovery.

FAQ

Q.01

Is OpenClaw hard to install?

Installing one on your own machine is quick if you meet the prerequisites. Running many reliably in production, with recovery and updates handled, is the hard part.

Q.02

What do I need to run OpenClaw?

A machine, a model provider key (or a local model), at least one channel to talk to it, and the project's required tooling.

Q.03

Can I run OpenClaw without installing it myself?

Yes. A managed OpenClaw hosting platform runs it for you, with recovery and integrations included, so you skip the setup and the on-call.

Want OpenClaw running without the setup and the babysitting? See managed hosting.