OpenClawOpenClaw
Self-hosted agent that lives in your existing chats
OpenClaw is an open-source agent runtime that runs on your machine and meets you in WhatsApp, Telegram, Slack, Discord and the rest. A Gateway sits in the middle: models, tools, channels and companion apps plug into one place. The ecosystem is the product. Setup and security are the tax.
[ 01 ] The verdict
The default if you want one agent across the chat apps you already live in, and you will own the box it runs on. Wrong default if you need a vendor to hold the keys or a learning loop that writes its own skills.
Best for
Builders who want a personal or small-team agent on their own hardware, talking over WhatsApp, Telegram, Slack or Discord rather than a new chat UI.
Watch out
A self-hosted agent with shell and browser tools is a security review, not a weekend install. Lock down who can talk to the gateway before you point it at production data.
Strengths
- Runs in the channels people already use instead of a new inbox
- Largest skill and plugin marketplace in this class (ClawHub)
- Model-agnostic: Claude, local models, OpenRouter, whatever you have keyed
- No seat or resolution bill from the project itself
Trade-offs
- You operate it: Node runtime, updates, access control, backups
- Default-open setups have burned people who skipped the security guide
- Less of a self-improving memory loop than Hermes
[ 02 ] What it actually does
What OpenClaw actually ships.
Gateway
One process routes models, tools and messaging channels. Personal laptop or a shared team deploy is a config difference, not a rewrite.
Channel coverage
WhatsApp, Telegram, Slack, Discord, iMessage and more, so the agent arrives where the conversation already is.
ClawHub skills
Installable skills and plugins rather than a closed action catalogue. The community is the integration layer.
Companion apps
Optional desktop and browser surfaces on top of the same gateway, including shared sessions in the 2.0 line.
[ 04 ] OpenClaw alternatives
