ClawHub

Setup

v1.0.0

Configure OpenClaw installations with optimized settings, channel setup, security hardening, and production recommendations.

2· 867· 1 versions· 5 current· 5 all-time· Updated 15h ago· MIT-0
byIván@ivangdavila

Quick Reference

TaskLoad
Messaging channels (Telegram, WhatsApp, Discord, etc.)channels.md
Agent settings, models, workspacesagents.md
Security, auth, DM policies, allowlistssecurity.md
Tools: exec, browser, web, mediatools.md
Cron, hooks, heartbeats, automationautomation.md
Recommendations by use caserecommendations.md
Memory search, embeddings, QMDmemory.md
Gateway: port, TLS, Tailscale, remotegateway.md

First Setup Checklist

Before any config, run:

openclaw onboard --install-daemon  # Full wizard
openclaw doctor                    # Check issues

Minimum viable config:

  • At least one channel connected (Telegram recommended for testing)
  • Model configured (Anthropic Claude or OpenAI)
  • Workspace path set (agents.defaults.workspace)
  • Owner allowlist configured (your user ID in channels.*.allowFrom)

Config Locations

FilePurpose
~/.openclaw/openclaw.jsonMain config
~/.openclaw/.envEnvironment variables
~/.openclaw/workspace/Default workspace
~/.openclaw/sessions/Session storage

Hot reload: Most settings apply instantly. Gateway settings (port, TLS) require restart.

Common Mistakes to Avoid

  1. Open DM policy without allowlist → Anyone can message your bot
  2. No auth token on remote gateway → Exposed to internet
  3. Model without fallbacks → Single point of failure
  4. Heartbeat without delivery target → Lost proactive messages
  5. exec.security: "full" in groups → Dangerous command access

When You're Done

openclaw doctor       # Verify config
openclaw status       # Check runtime
openclaw health       # Gateway health

Version tags

latestvk978gs2vmebks6m1h3wmrj06sd8121sx