Connect your Rocket.Chat server directly to OpenClaw agents—no bridge server needed.
- A Rocket.Chat server (with admin access)
- OpenClaw installed and configured with an AI provider
- A default agent already set up
Having issues? Check
openclaw.examples.jsonin the repo root for a complete annotated configuration reference. You can also manually edit~/.openclaw/openclaw.jsonif needed.
Checkout : SETUP.md Full installation, credentials & email setup
openclaw plugins install clawhub:@dodaa08/openclaw-plugin-test
openclaw rocketchat setupThe wizard will:
- Ask for your Rocket.Chat server URL and admin login
- Create a bot user on your server
- Create or bind an OpenClaw agent
- Write bot config to
~/.openclaw/openclaw.json
Then verify in Rocket.Chat by DMing the bot:
You should see gateway - online and runtime - ready.
Credentials are stored securely in
~/.openclaw/credentials/(owner-only permissions).
| Command | Description |
|---|---|
!help |
Show all commands |
!status |
Gateway + connection status |
!bots |
List bots and agents |
!add-bot <user> |
Create a new bot (owner) |
!remove-bot <user...> |
Delete bot(s) (owner) |
!lend <group> <user> |
Grant access |
!revoke <group> <user> |
Revoke access |
!model / !model set <name> |
Show or switch model |
!compact |
Compress conversation history |
!reset |
Wipe context |
!new [model] |
Start fresh conversation |
!think <level> |
Set thinking depth (off / low / medium / high) |
!abort |
Stop current reply |
- All data stays on your machine — no cloud uploads
- Each bot is isolated (own connection, own agent, own access grants)
- Admin token is only used during setup and can be deleted afterward
| Doc | Description |
|---|---|
| ARCHITECTURE.md | How the plugin works (DDP + REST, multi-bot, security) |
| COMMANDS.md | Complete command reference |
| SKILLS.md | Installing & managing skills (global vs per-agent) |
| SETUP.md | Full installation, credentials & email setup |
| CONTRIBUTING.md | Contributors guide |
When users send media (images, audio, etc.) in Rocket.Chat, the plugin downloads the files locally to ~/.openclaw/media/inbound/.
- Why locally? This allows the OpenClaw agent to reliably process the actual file bytes from the filesystem rather than struggling with URL authentication or timeouts.
- Limits: The plugin currently caps downloads at 20MB per file and supports
image/,audio/,video/, andapplication/MIME types. - Cleanup: Currently, there is no automatic auto-prune for these files. We recommend users set up a cron job to clean up the folder periodically, e.g.:
find ~/.openclaw/media/inbound -type f -mtime +7 -delete.
Future enhancements currently being tracked:
- Expanding End-to-End (E2E) and integration test coverage across the repository.
- Preparing project for official v1 release.
- Addressing remaining bugs and structural updates from our internal trackers: