Openclaw (formerly Clawdbot & Moltbot) is an open-source, self-hosted personal AI assistant that runs locally on your devices and integrates with messaging platforms like WhatsApp, Telegram, Discord, Slack, and iMessage.
The assistant uses a local Gateway server to connect your chosen AI model (like Claude) to everyday communication channels. You can control it entirely through text messages sent from platforms you already use.
Your data stays on your device, the assistant remembers context between conversations, and it can perform actual system-level operations like managing files, running scripts, and automating browser tasks.
OpenClaw is ideal for technical users who want a self-hosted AI assistant that can handle real tasks from chat, voice, browser automation, files, scripts, calendars, reminders, and connected apps.
It is not a simple chatbot. It is closer to a local AI operator that can act across your computer and communication channels.
Features
- Runs through a local Gateway that controls sessions, channels, tools, and events.
- Connects to WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, IRC, Microsoft Teams, Matrix, Feishu, LINE, Mattermost, Nextcloud Talk, Nostr, Synology Chat, Tlon, Twitch, Zalo, Zalo Personal, WeChat, QQ, and WebChat.
- Supports voice wake and talk mode on macOS, iOS, and Android.
- Provides a Live Canvas for agent-driven visual output and UI surfaces.
- Uses browser, canvas, nodes, cron, sessions, and channel action tools.
- Supports bundled skills, workspace skills, managed skills, and ClawHub resources.
- Supports multiple model providers through model configuration and provider catalogs.
- Uses DM pairing by default for unknown senders on major direct-message channels.
- Supports sandboxing for non-main sessions through Docker, SSH, or OpenShell backends.
- Includes optional companion apps and nodes for macOS, iOS, and Android.
Use cases
Personal productivity
OpenClaw can send morning briefings, schedule follow-up reminders, summarize messages, monitor tasks, prepare checklists, and respond through the channel you already use.
Developer workflows
OpenClaw can run shell commands, inspect files, review logs, manage Git workflows, interact with browser sessions, and route tasks to agent sessions from chat or the CLI.
Research and monitoring
OpenClaw can collect information, summarize pages, watch sources, process structured data, and deliver updates through configured channels.
Content and publishing
OpenClaw can draft outlines, prepare social posts, manage repeated publishing workflows, and use scheduled jobs or webhooks for recurring tasks.
Voice and meeting workflows
OpenClaw supports voice wake, talk mode, and voice-related automation. Recent releases also added deeper realtime voice diagnostics and Google Meet-related voice work.
Home and device automation
OpenClaw can connect agent actions to local tools, paired nodes, browser control, and external services. The exact capability depends on your installed tools, channel setup, and security policy.
Real-world Use Cases
How to use OpenClaw
1. Install Node.js first. OpenClaw recommends Node 24 and supports Node 22.16 or later. Windows users should use WSL2 for the best supported setup path.
2. Install OpenClaw globally with npm or pnpm.
npm install -g openclaw@latestpnpm add -g openclaw@latest3. Start the guided setup.
openclaw onboard --install-daemon4. Choose your model provider and authentication method during onboarding. OpenClaw supports many providers and models, but you should use a current model from a provider you already trust.
5. Connect your messaging channels. Telegram usually needs a bot token. WhatsApp usually needs device linking. Discord, Slack, Google Chat, and other channels have their own setup requirements.
6. Keep the default DM pairing policy unless you understand the security tradeoff. Unknown direct-message senders receive a pairing code, and OpenClaw does not process their message until you approve access.
7. Start the Gateway manually if you want verbose logs.
openclaw gateway --port 18789 --verbose8. Send a test message through a configured channel or from the CLI.
openclaw message send --target +1234567890 --message "Hello from OpenClaw"9. Send a direct terminal request to the assistant.
openclaw agent --message "Ship checklist" --thinking high10. Run diagnostics after installation or updates.
openclaw doctorCommand Reference
| Command | What it does |
|---|---|
openclaw onboard --install-daemon | Runs guided setup and installs the Gateway daemon. |
openclaw gateway --port 18789 --verbose | Starts the Gateway manually with detailed logs. |
openclaw agent --message "your text" --thinking high | Sends a direct CLI message to the assistant. |
openclaw message send --target +1234567890 --message "text" | Sends a message through a configured channel target. |
openclaw pairing approve <channel> <code> | Approves a new sender after DM pairing. |
openclaw doctor | Checks configuration, setup, and common failure points. |
openclaw update --channel stable | Updates through the stable release channel. |
openclaw update --channel beta | Switches to beta releases. |
openclaw update --channel dev | Uses the moving development channel when published. |
openclaw nodes list | Lists connected device nodes. |
openclaw plugins list --json | Shows plugin state in JSON format. |
openclaw cron list --json | Shows cron jobs and computed job status in JSON format. |
Chat Commands
Send these in WhatsApp/Telegram/etc.
| Command | What it does |
|---|---|
/new | Starts a fresh session. |
/reset | Clears the current session context. |
/status | Shows current model, token usage, and session state. |
/think <level> | Sets reasoning level for supported models. |
/think default | Clears the current thinking override. |
/fast default | Clears the current fast-mode override. |
/compact | Summarizes conversation context. |
/verbose on | Turns detailed response logging on. |
/verbose off | Turns detailed response logging off. |
/usage off | Hides token usage output. |
/usage tokens | Shows token usage. |
/usage full | Shows fuller usage details. |
/restart | Restarts the Gateway process for the owner. |
/activation mention | Replies only when mentioned in group contexts. |
/activation always | Replies more broadly in allowed group contexts. |
/steer <message> | Steers an active current-session run. |
/side | Sends a side question alias for the BTW flow. |
Key Settings
The main configuration file is:
~/.openclaw/openclaw.jsonA minimal model configuration looks like this:
{
agent: {
model: "<provider>/<model-id>"
}
}The default agent workspace is:
~/.openclaw/workspaceOpenClaw injects these prompt files into the agent workspace when configured:
AGENTS.md
SOUL.md
TOOLS.mdWorkspace skills live under:
~/.openclaw/workspace/skills/<skill>/SKILL.mdSupported messaging channels
| Channel or surface | Notes |
|---|---|
| Messaging channel with setup requirements. | |
| Telegram | Bot-based channel setup. |
| Slack | Workspace channel and DM workflows. |
| Discord | Bot and channel workflows. |
| Google Chat | Supported channel. |
| Signal | Supported direct-message channel. |
| iMessage | Supported Apple messaging surface. |
| IRC | Supported chat channel. |
| Microsoft Teams | Supported work messaging channel. |
| Matrix | Supported open messaging channel. |
| Feishu | Supported work messaging channel. |
| LINE | Supported messaging channel. |
| Mattermost | Supported team chat channel. |
| Nextcloud Talk | Supported collaboration channel. |
| Nostr | Supported protocol surface. |
| Synology Chat | Supported chat channel. |
| Tlon | Supported channel. |
| Twitch | Supported community channel. |
| Zalo | Supported messaging channel. |
| Zalo Personal | Supported personal messaging channel. |
| Supported messaging channel. | |
| Supported messaging channel. | |
| WebChat | Browser-based chat surface. |
Security and privacy
OpenClaw is self-hosted, but it can access sensitive local resources after you configure tools and channels. The safest setup keeps the Gateway bound to localhost, uses DM pairing, limits approved senders, and keeps powerful tools away from untrusted sessions.
Direct messages use pairing by default on major supported channels. Unknown senders receive a pairing code, and OpenClaw does not process their messages until you approve them.
Public inbound DMs require an explicit opt-in. Do not use open DM policy with wildcard allowlists unless you understand the risk.
The main session can run tools on the host. Non-main sessions should use sandbox mode when group chats, public channels, or other less trusted inputs can reach the assistant.
Optional apps and nodes
OpenClaw can run as a Gateway alone. Optional apps and nodes add extra surfaces.
macOS app
The macOS app can provide menu bar Gateway control, health status, voice wake, push-to-talk, WebChat, debug tools, and remote Gateway control over SSH.
iOS node
The iOS node can pair with the Gateway over WebSocket, forward voice triggers, provide a Canvas surface, and respond to node commands.
Android node
The Android node can pair over WebSocket and expose Connect, Chat, Voice, Canvas, Camera, Screen Capture, and Android device command families.
Pros
- Open-source code.
- Self-hosted Gateway.
- Various channels support.
- Voice support.
- Live Canvas.
- Strong automation surface.
- Flexible model routing.
- Useful setup wizard.
Cons
- Technical setup required.
- API costs may apply.
- Channel setup varies.
- Security needs care.
- Beta releases can change quickly.
- Host tools carry risk.
Related resources
- OpenClaw GitHub repository: View source code, releases, issues, and license details.
- OpenClaw documentation: Read the full setup, channel, Gateway, security, and tool docs.
- Getting started guide: Follow the beginner setup path for a new install.
- Onboarding guide: Learn how the guided CLI setup works.
- Updating guide: Update OpenClaw and switch release channels.
- Security documentation: Review DM policy, remote access, and Gateway safety.
- Skills documentation: Learn how OpenClaw skills work.
- 7 Best OpenClaw Alternatives: Compare OpenClaw with other local AI agent projects.
- NanoClaw: Check a lighter OpenClaw alternative.
FAQs
Q: Can Openclaw really automate my entire workflow?
A: It depends on your workflow complexity and technical comfort level. Simple tasks like file organization, calendar checks, and basic research work immediately after installation. Advanced automation like multi-platform social posting, complex trading alerts, or custom business workflows require hours of setup time. You’ll need to build skills, configure API access, and test thoroughly.
Q: Is my data safe with a self-hosted assistant?
A: Your data stays on your hardware and only leaves your network when you explicitly configure external API calls. This is more private than cloud-based assistants. However, you’re responsible for security. Use the default pairing mode for DM access, run non-main sessions in sandboxed environments, and never expose the Gateway to the public internet without proper authentication.
Q: What happens if the Gateway crashes or my computer restarts?
A: The daemon installation (recommended setup) automatically restarts the Gateway when your system boots and recovers from crashes. Conversations persist through restarts because the session data is stored on disk. You might miss messages that arrive during downtime, but the assistant picks up where it left off once running again.
Q: How does Openclaw compare to ChatGPT or Claude directly?
A: ChatGPT and Claude are pure conversational interfaces. They answer questions but can’t execute tasks on your computer. Openclaw uses these models as reasoning engines but adds the ability to actually perform actions like managing files, running scripts, controlling browsers, and automating workflows. Think of it as giving ChatGPT hands and letting it work while you’re away from your desk.
Q: Can multiple people share the same Openclaw instance?
A: You can configure multi-user access, but it’s designed as a personal assistant. Each person would see all conversations and share the same context. A better approach is running separate Gateway instances for each person with their own configurations and workspaces. The multi-agent coordination features let different instances communicate when needed.
Changelog
05/10/2026
- Tons of updates
01/30/2026
- Renamed to Openclaw
- Tons of updates
01/27/2026
- Renamed to Moltbot
