← All templates
ai / SETUP GUIDE

Openclaw

WhatsApp gateway CLI with Pi RPC agent - self-hosted AI-powered messaging platform

Before you start

  • browser: review Compose shm_size=2g; no implicit host privileges or configuration mounts

Configuration that needs your attention

This migration candidate preserves supported service, storage and credential declarations. Resolve every prerequisite before deployment.

Candidate credential references

This draft lists possible credential bindings. Some providers are alternatives. Finalize the required bindings after resolving the migration prerequisites; do not create every listed provider account.

  • ai-gateway-api-key
  • anthropic-api-key
  • auth-password
  • aws-access-key-id
  • aws-secret-access-key
  • aws-session-token
  • cerebras-api-key
  • copilot-github-token
  • deepgram-api-key
  • discord-bot-token
  • gemini-api-key
  • groq-api-key
  • kimi-api-key
  • minimax-api-key
  • mistral-api-key
  • moonshot-api-key
  • openai-api-key
  • openclaw-gateway-token
  • opencode-api-key
  • openrouter-api-key
  • slack-app-token
  • slack-bot-token
  • synthetic-api-key
  • telegram-bot-token
  • venice-api-key
  • xai-api-key
  • xiaomi-api-key
  • zai-api-key

Complete the prerequisites

This migration is not enabled for deployment. Resolve the prerequisites listed above and validate startup, networking and persistent storage before using it.

Read the upstream setup documentation ↗

View migration status and native candidate ↗