Features
Highlights
Channels
WhatsApp, Telegram, Discord, Slack, Teams, Google Chat, Matrix, Zalo, and BlueBubbles.
Multi-agent routing
Isolated sessions per agent or sender. Switch with /agent.
Media
Images, audio, and documents in and out via provider APIs.
Control UI
Browser-based chat and admin dashboard at <tenant>.clawcentral.io.
Skills & automation
Cloud-managed skills and cron automation.
Voice (browser)
Browser-based wake word detection and TTS in the Control UI.
Available in ClawCentral
Messaging channels
- Telegram bot (outbound + inbound)
- Discord bot (outbound + inbound)
- Slack bot (outbound + inbound, slash commands)
- WhatsApp (outbound + inbound via WhatsApp Business API)
- Microsoft Teams (outbound + inbound via Bot Framework)
- Google Chat (outbound + inbound)
- Matrix (outbound + inbound via Application Service)
- Zalo (outbound + inbound)
- BlueBubbles (outbound + inbound — iMessage via BlueBubbles server)
- WebChat (built into the Control UI)
Agent features
- AI agent chat with streaming responses
- Multi-agent routing — switch between named agents with
/agent - Session isolation per agent, channel, or sender
- Skills — cloud-managed, installable from the admin panel
- Automation and cron — scheduled runs, hooks
- Multi-turn memory (conversation history stored in ClawCentral's cloud storage)
Media
- Inbound images, audio, and documents (surfaced to the agent via provider APIs)
- Outbound media attachments
- Voice note transcription (via configured provider)
- TTS (text-to-speech) for voice responses
Control UI
- Browser-based chat interface at
<tenant>.clawcentral.io - Admin panel: channels, providers, skills, agents, sessions
- Voice mode with browser-based wake word detection
- Paired node management (Nodes tab)
AI providers
- Anthropic (Claude)
- OpenAI (GPT)
- Google (Gemini)
- Additional providers via custom OpenAI-compatible or Anthropic-compatible endpoints
- Optional AI gateway proxy for caching, rate limiting, and usage analytics
How ClawCentral differs from self-hosted
Some capabilities work differently in ClawCentral compared to a self-hosted OpenClaw gateway. In most cases, ClawCentral provides a managed alternative.
Code execution and workspace
| Self-hosted | ClawCentral |
|---|---|
| Local shell, file system, CLI tools | Sandboxed container with Python, Node.js, Bash, Go, Rust, and Bun — isolated per user |
| Agent workspace on local disk | Cloud workspace with workspace_read, workspace_write, workspace_ls — persistent per-user storage in R2 |
Agent files (AGENTS.md, SOUL.md, etc.) on local filesystem | Same files, managed in cloud storage and editable from the Admin UI |
Device integrations
These require a locally running gateway or paired node and are not available in the managed cloud:
- Camera and screen capture — local macOS/iOS/Android device integrations. Available via paired nodes.
- Local voice — native OS microphone/speaker APIs. ClawCentral offers browser-based voice mode in the Control UI instead.
Self-hosted operations
Not applicable to a managed service:
- Running your own gateway process, daemon install, or systemd units
- Tailscale exposure of a local gateway
- CLI-based onboarding wizard
Channel differences
| Channel | Self-hosted | ClawCentral |
|---|---|---|
| iMessage | Legacy imsg CLI (local macOS) | BlueBubbles-based iMessage channel |
| WhatsApp Web / Baileys | Official WhatsApp Business API | |
| Signal | Local signal-cli server | Not available |
| Mattermost | Self-hosted plugin | Not available |