OpenClaw

Multi-project AI operating system — orchestration core, control channels (Telegram/WhatsApp), integrations, and per-project profiles.

Quick start (standalone)

cd "Open Claw"   # or your clone path, e.g. /opt/openclaw
npm install
npm run openclaw:build
npm run openclaw:test

Requirements: Node.js 20+

Project layout

core/                 # Orchestration engine + project profile loader
control/              # Telegram + WhatsApp command router
command-center/       # Founder web dashboard
agents/               # Agent packs
integrations/         # Gmail, leads, workflows, CRM, etc.
projects/             # Per-tenant profiles (data + config)
  zonforge/           # ZonForge Sentinel (default)
templates/project/    # Scaffold for new projects
scripts/              # Build, deploy, health checks
deploy/               # systemd units
docs/
logs/                 # Runtime logs (gitignored)
output/               # Legacy shared output (gitignored)

Set OPENCLAW_ROOT to this directory if you run commands from elsewhere.

Run control locally

Telegram

cp control/.env.example control/.env
# Edit secrets, then:
npm run openclaw:dev

WhatsApp

cp control/.env.whatsapp.example control/.env.whatsapp
npm run openclaw:whatsapp:dev

ZonForge profile

ZonForge ships as the default project: projects/zonforge/.

Item	Location
Config	projects/zonforge/config.yaml
ICP / lead gen	projects/zonforge/lead-generation.yaml
Outputs	projects/zonforge/output/
KPIs	projects/zonforge/data/dashboard/
Audit	projects/zonforge/audit/commands.jsonl

Default project id: zonforge (OPENCLAW_PROJECT=zonforge).

Switch at runtime: /project list, /project zonforge, /project cpa-workflow.

Migrate legacy flat output/ and data/ into the profile:

bash scripts/migrate-to-project-profiles.sh

Add a new project

1. Copy templates/project/ → projects/<your-id>/
2. Edit config.yaml, lead-generation.yaml, agents.yaml, workflows.yaml, security.yaml
3. Add prompts under projects/<your-id>/prompts/
4. Set OPENCLAW_PROJECT=<your-id> or use /project <your-id>

See docs/PROJECT_PROFILES.md.

Deploy WhatsApp control (production)

Target install path: /opt/openclaw

1. Clone this repo on the VPS:

   git clone <your-openclaw-repo-url> /opt/openclaw
   cd /opt/openclaw

2. Configure secrets:

   cp control/.env.whatsapp.example control/.env.whatsapp
   chmod 600 control/.env.whatsapp

3. Build and install systemd unit:

   npm install
   npm run openclaw:build
   sudo bash scripts/deploy-whatsapp-vps.sh

   Or use scripts/deploy-stage2-production.sh for git-pull + backup + restart workflow.

4. Health check:

   bash scripts/health-whatsapp.sh verify
   curl -s http://127.0.0.1:3026/health

systemd unit: deploy/openclaw-whatsapp.service
Start script: scripts/start-whatsapp.sh

Full guide: docs/WHATSAPP_DEPLOYMENT.md

Scripts reference

Script	Purpose
npm run openclaw:build	Build all workspaces in order
npm run openclaw:test	Run all package tests
scripts/start-whatsapp.sh	Production WhatsApp entry (systemd)
scripts/start-telegram.sh	Production Telegram entry
scripts/deploy-whatsapp-vps.sh	VPS install / restart
scripts/migrate-to-project-profiles.sh	Legacy → project-scoped data

Packages

Workspaces use the @openclaw/* scope (@openclaw/core, @openclaw/control, etc.).

Security

Never commit .env, .env.whatsapp, or API keys. Templates use *.example only.