Getting Started with OpenClaw

Use this guide to stand up a secure, stable, high-leverage OpenClaw environment quickly.

Recommended Hardware

Use least-privilege defaults and explicit allowlists
Keep gateway local-only unless remote access is required
Never expose download/checkout flows without verification
Use a vault OpenClaw can access (for example, Bitwarden) for secrets management
Store all tokens, passwords, API keys, and credentials in the vault (not in plain files/chat)
Rotate credentials/tokens periodically and after sharing
Review logs and alerts on a daily cadence

Copy and paste these commands in order on macOS.

Install Homebrew
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
Install Node.js LTS + Git
brew install node git
node -v && npm -v
Install OpenClaw CLI globally
npm i -g openclaw
openclaw --version
Create and move to your workspace
mkdir -p ~/.openclaw/workspace && cd ~/.openclaw/workspace
Run guided setup / checks
openclaw doctor
Check service status
openclaw status
Start gateway if needed
openclaw gateway start
openclaw gateway status
Connect WhatsApp (optional)
openclaw whatsapp login
Scan QR, then send yourself a test message.
Verify everything
openclaw logs --limit 120 --plain --local-time

Security baseline after install: keep gateway local-only first, enable allowlists, and avoid exposing endpoints publicly until hardened.

Use this rollout plan for the fastest path to implement security best practices, stable workflows, and critical OpenClaw infrastructure correctly.

Start with one critical workflow and clear success metric.
Use: Starter Operator Stack — fastest path to establish baseline execution discipline.
View Bundle
Pilot with a small scope before scaling.
Use: Personal Ops Starter + Meeting Ops Pack — validate execution quality with limited risk.
View Build Kit View Build Kit
Add approval gates on sensitive actions.
Use: Security Control Bundle — adds safer controls and approval patterns.
View Bundle
Introduce reminders/alerts after base flow stabilizes.
Use: WhatsApp Automation Pack + Execution Core — adds real-time reminders once workflows are stable.
View Build Kit View Bundle
Document handoffs and rollback steps.
Use: Shared Brain Builder (or Team Throughput System for multi-role teams) — improves continuity and recovery readiness.
View Build Kit View Bundle