Skip to main content
ClawDock is a small shell-helper layer for Docker-based OpenClaw installs. It gives you short commands like clawdock-start, clawdock-dashboard, and clawdock-fix-token instead of longer docker compose ... invocations. If you have not set up Docker yet, start with Docker.

Install

If you previously installed ClawDock from scripts/shell-helpers/clawdock-helpers.sh, reinstall from the current scripts/clawdock/clawdock-helpers.sh path; the old raw GitHub path was removed. The helpers auto-detect your OpenClaw checkout on first use (checking common paths like ~/openclaw, ~/projects/openclaw) and cache the result in ~/.clawdock/config. Set CLAWDOCK_DIR yourself if your checkout lives elsewhere.

What you get

Basic operations

Container access

Web UI and pairing

Setup and maintenance

Utilities

First-time flow

If the browser says pairing is required:

Config and secrets

ClawDock reads two separate .env files, matching the split described in Docker:
  • The project .env next to docker-compose.yml: Docker-specific values like image name, ports, and OPENCLAW_GATEWAY_TOKEN. clawdock-token reads the token from here.
  • ~/.openclaw/.env (mounted into the container): env-backed secrets OpenClaw itself manages, alongside openclaw.json and agents/<agentId>/agent/auth-profiles.json.
clawdock-fix-token copies the token from the project .env into the container’s gateway.remote.token and gateway.auth.token config values and restarts the gateway. Use clawdock-show-config to inspect openclaw.json and both .env files quickly; it redacts .env values in its printed output.

Docker

Canonical Docker install for OpenClaw.

Docker VM runtime

Docker-managed VM runtime for hardened isolation.

Updating

Updating the OpenClaw package and managed services.