Super Claw
Chapter 1 of 16
PHASE 1: Launch Sequence
Chapter 1

Pre-Flight Check

Get OpenClaw running and meet the SuperClaw CLI

Before deploying SuperClaw, you need OpenClaw running. This chapter gets your AI backend online and introduces the SuperClaw CLI — your tool for installing and managing the SuperClaw dashboard.

What is SuperClaw?

SuperClaw is two things working together, sitting on top of OpenClaw.

SuperClaw CLI

A command-line tool you install globally. It handles setting up and managing the SuperClaw dashboard — installs it, manages admin users, handles Pro licence activation, and keeps everything updated.

SuperClaw Dashboard

A web interface that sits on top of your OpenClaw instance. Visibility into your sessions, agents, usage, and workspace. The CLI installs it; you access it through a browser.

OpenClaw is the AI backend that does the actual work — conversations, memory, tools, channel integrations. SuperClaw doesn't extend what OpenClaw can do. It gives you a proper interface for controlling and monitoring it.

System Requirements

  • Node.js 18+ — runtime for both OpenClaw and the dashboard
  • Terminal access — you'll be running CLI commands throughout this guide
  • An AI provider account — OpenClaw works with Claude, OpenAI, Gemini, and others. Claude is recommended and used by default
# Verify Node.js version
node --version
# Should show v18.0.0 or higher

Do You Need Memory Embeddings?

Short answer: if you're running multiple agents and more than one person is messaging your AI, yes.

Here's why it matters. Imagine you run a two-person business — you and a partner. You've both connected to OpenClaw via Slack. You're in #dev talking about a bug in your checkout flow. Your partner is in #marketing asking about last quarter's campaign results. A third channel, #support, is fielding customer questions.

Over time, three specialized agents build up their own memory:

Developer Agent

Knows your codebase, deployment setup, and every engineering decision you've made. #dev is its home.

Marketing Agent

Knows campaign history, your audience, what's worked and what hasn't. Lives in #marketing.

Support Agent

Knows your customers, common issues, how you like complaints handled. Runs #support.

This is exactly what SuperClaw is built for. The message router sends "fix the checkout bug" to the right agent automatically, regardless of which of you sent it. Each agent maintains isolated memory so context doesn't bleed between domains.

But here's what happens after a few months: memory gets wide. The developer agent remembers 50 technical decisions. The marketing agent has campaign notes going back to launch. The support agent has patterns from hundreds of customer interactions. And sometimes the context you need sits across all of them — a customer complaint that's actually a billing bug that marketing accidentally mentioned in a campaign brief.

Without embeddings, your AI searches memory by keyword — it finds what you literally said. With embeddings, it finds what you meant. A question like "what was the issue with the payment flow last quarter?" retrieves the right thread even if nobody used those exact words at the time.

Solo user, one agent: embeddings are useful but not critical.

Two people, multiple agents across channels: embeddings are what make the memory useful as it scales. Without them you're indexing a filing cabinet alphabetically. With them you're searching it by meaning.

Setting Up an Embedding Provider

The easiest free option is Gemini. Grab a key from Google AI Studio in about two minutes, then run:

openclaw auth add --provider gemini
Can I skip this for now?

Yes. OpenClaw falls back to keyword search without an embedding provider — everything still works, it just gets less precise as your agents accumulate context. You can add a provider any time without losing existing memory.


Step 1: Install OpenClaw

npm install -g openclaw

Verify it's working:

openclaw --version

Step 2: Configure OpenClaw

Run the interactive setup wizard:

openclaw configure

This walks you through:

  • Connecting your AI provider (Anthropic recommended — uses your Claude subscription via OAuth, or paste an API key from console.anthropic.com)
  • Configuring your workspace directory
  • Setting up any channel integrations (Slack, Telegram, Discord, etc.)
Using Claude?

You don't need an API key if you have a Claude.ai subscription. The setup wizard lets you authenticate via OAuth — it's the same account you already log into at claude.ai.

Step 3: Start the Gateway

openclaw gateway start

The Gateway is the core OpenClaw process — it handles AI conversations, message routing, and tool execution. It runs in the background and stays running.

Check it's healthy:

openclaw health

Step 4: Install the SuperClaw CLI

npm install -g @skunkceo/superclaw-cli

Verify it installed:

superclaw version

Step 5: Install the Dashboard

superclaw init

This clones the SuperClaw dashboard from GitHub and sets it up locally. The wizard asks where you want to install it and walks you through creating your first admin account.

Once installed, access the dashboard at the URL shown in the output (typically http://localhost:3000).


SuperClaw CLI Reference

CommandWhat it does
superclaw initInstall the SuperClaw dashboard
superclaw statusHealth check — dashboard, gateway, versions
superclaw updateUpdate the CLI and dashboard
superclaw update --checkCheck for available updates without installing
superclaw doctorDiagnose and fix common issues
superclaw setupCreate or manage dashboard admin users
superclaw pro install <key>Activate a Pro licence
superclaw pro statusCheck your Pro licence status

Free vs Pro Dashboard

Free — included

    Pro — from $5/mo

      Ready to go Pro?

      Unlock smart routing, scheduled jobs, team management, and the skills marketplace with a Pro licence.

      Get SuperClaw Pro

      Time Investment

      This chapter: ~15 minutes Full guide: ~2 to 3 hours


      Chapter Checklist

      Before moving to Chapter 2, make sure you can tick these off:

      • Node.js 18+ installed
      • OpenClaw installed and configured (openclaw configure complete)
      • Gateway running (openclaw health returns OK)
      • SuperClaw CLI installed (superclaw version works)
      • Dashboard installed and accessible in browser (superclaw init complete)

      Next: Chapter 2 covers the ignition sequence — first boot, workspace setup, and getting your AI talking.