OpenClaw Installation Checklist: From Zero to First Working Session

Most OpenClaw installations fail before they start. Not because the software is hard to install, but because people skip environment checks, rush through configuration, and end up debugging problems that a simple pre-flight checklist would have caught.

This guide is the checklist we use internally at Invatechs. Every client setup starts here. If you follow it top-to-bottom, your first OpenClaw session will actually work.

Before You Touch the Installer

OpenClaw requires a few things from your machine. None of these are unusual, but missing any one of them will cause confusing errors later.

Machine Prerequisites

• Operating system: macOS 12+, Ubuntu 20.04+, or Debian 11+. Windows works under WSL2, but native Linux or macOS is simpler.
• Node.js 18+: Run node --version to confirm. If you're below 18, upgrade before proceeding. NVM makes this painless.
• Git 2.30+: OpenClaw pulls configuration from repos. Older Git versions cause silent auth failures with modern token-based workflows.
• Disk space: At least 2 GB free. OpenClaw caches models and session data locally.
• Network access: OpenClaw needs outbound HTTPS on ports 443 and 8443. If you're behind a corporate proxy, configure your HTTPS_PROXY environment variable first.

API Keys and Tokens

Before installation, have these ready in a secure location (not a sticky note):

• Your OpenClaw license key or activation token
• API keys for any AI providers you plan to connect (Anthropic, OpenAI, etc.)
• Bot tokens for your messaging channels (Telegram, Discord, or both)
• A GitHub/GitLab personal access token if OpenClaw will interact with repos

Store these in a .env file in the OpenClaw root directory. Never commit this file. Add it to your .gitignore immediately.

Installation Steps

Step 1: Clone and Bootstrap

If npm install takes more than five minutes or throws errors, check that your Node version is correct. The most common failure here is running Node 16 instead of 18+.

Step 2: Environment Configuration

Open the .env file and fill in every required field. Don't leave placeholder values. OpenClaw won't warn you about missing keys until you actually try to use the feature that needs them, which creates confusing "it worked yesterday" situations.

Step 3: Initial Safety Profile

OpenClaw ships with three built-in safety profiles: restrictive, standard, and permissive. For your first install, use standard.

The restrictive profile blocks too many actions for a useful first session. The permissive profile is designed for experienced operators who understand the risk surface. Start in the middle, then adjust.

Step 4: Connect Your First Channel

Pick one channel to start with. Not two, not three. One. Whether that's Telegram or Discord, the goal is to confirm the full communication loop works before adding complexity.

The channel test command sends a round-trip ping. If you see a confirmation message in your Telegram chat, you're connected. If you don't, check your bot token and make sure your bot has been added to the target group or channel.

Validating Your First Command Flow

Installation is not done when the software runs. It's done when you've completed one real task end-to-end. Here's a sequence that tests every layer of the stack:

1. Send a simple message through your connected channel. "What time is it?" works. Confirm OpenClaw responds.
2. Ask it to read a file from a connected repo. This tests Git access, file system permissions, and the tool execution pipeline.
3. Ask it to create a file and commit it to a test branch. This confirms write access, branch creation, and the safety profile allows it.
4. Check the session log. Run openclaw log --last and verify you can see a clear record of what happened.

Post-Install Hardening

Once your first session works, do these three things before you walk away:

• Review the access log. Check what tools OpenClaw invoked and whether that matches your expectations. If something looks off, tighten the safety profile or add explicit deny rules.
• Set up a backup. Your .env file and config/ directory are the only two things you need to reconstruct a working setup. Back them up somewhere that isn't the same machine.
• Document what you did. Write a one-paragraph note about your setup: which channel, which safety profile, which repos. Future-you will thank present-you when something needs debugging at 11 PM.

Common First-Install Mistakes

We've done hundreds of these installs. These are the five mistakes that show up the most:

1. Skipping the channel test. People assume if the bot token is valid, the connection works. It doesn't. Bot permissions, group settings, and webhook configurations all need to be right.
2. Using placeholder .env values. The installer doesn't validate every key at startup. You'll discover the problem mid-task, not during installation.
3. Running on Node 16. The error messages when running on an old Node version don't mention Node. They mention obscure module resolution failures.
4. Starting with the permissive safety profile. This creates a false sense of what OpenClaw "normally" does. Start with standard so you understand the guardrails before removing them.
5. Not testing write operations. Read access works? Good. But most real workflows involve creating, editing, or committing files. Test the full loop.

Your Checklist, Summarized

• Machine prerequisites confirmed (OS, Node 18+, Git 2.30+, disk space, network)
• API keys and bot tokens collected and stored in .env
• OpenClaw cloned and dependencies installed
• Safety profile set to standard
• One channel connected and tested with round-trip ping
• Full command flow validated (read, write, commit, log check)
• Access log reviewed
• Config backed up
• Setup documented

That's the full path from zero to a working OpenClaw session. If you followed this checklist, you now have a verified, documented installation that you can build on with confidence.