Installing OpenClaw: A First-Timer's Guide

OpenClaw is often described as a personal AI assistant, but that undersells it. It is closer to a programmable colleague — one that stays available around the clock, connects to the tools you already use, and gets more capable the more you teach it. This guide takes you from a blank machine to a working installation, assuming no prior experience with AI infrastructure.

What you need before you start

Three things need to be in place, and it is worth gathering all of them before you run a single command.

• An API key for a language model. Most people start with Anthropic's Claude. Create an account, generate a key, and keep it somewhere safe — you will paste it into a config file shortly.
• A communication channel. Discord is the most common starting point because its bot integration is well documented. You will need a bot token from a Discord application you control.
• A machine to run it on. Your laptop is fine for getting started. For an assistant that runs permanently, a small cloud VM or a home server is better. OpenClaw is a Node.js application, so anything running a recent Node version will work.

Installing OpenClaw

With prerequisites ready, the install itself is short:

1. Confirm Node.js is present by running node --version. If you see a version number, continue; if not, install Node first.
2. Download OpenClaw from the official source — clone the repository if you are comfortable with Git, or download and extract the archive to a permanent location.
3. From inside the project folder, run npm install to pull dependencies.
4. Copy the example environment file to .env, then paste in your model API key and your Discord bot token.
5. Run the start command and watch the terminal. Within seconds you should see the assistant connect.

Now go to your Discord channel and type hello. If the assistant replies, your installation is working. That moment — a message you wrote getting an intelligent answer back through your own infrastructure — is the whole point.

The first thing to do once it works

A freshly installed assistant can hold a conversation but cannot yet do much. Its usefulness comes from skills — small, focused capabilities that let it read your calendar, run commands, search the web, or query a database.

Resist the urge to install a dozen at once. Start with one that gives the assistant context about your work, test it on a real task, and only then add the next. We wrote a separate guide on choosing your first OpenClaw skills that walks through a sensible starting set, and you can browse the full catalogue on our ClawHub skills directory.

Where people get stuck

Most failed installs are not really installation problems — they are configuration problems that surface later. The two most common:

• A skill that needs credentials. Many skills require an API key or an OAuth grant before they do anything. Read each skill's README before the first use rather than debugging a silent failure afterward.
• Giving the assistant too much access too fast. If your assistant can run shell commands, start with low-stakes requests on a machine you do not mind experimenting on, and widen its scope as you build confidence.

Getting all of this right — the model choice, the channel setup, the skill selection, and sensible permission boundaries — is exactly the work we do for clients. If you would rather have a working, well-configured setup without the trial and error, talk to us about your OpenClaw setup.

Related posts

• Choosing Your First OpenClaw Skills