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 |
|---|---|
| SETUP.md | Full installation, credentials & email setup |
| ARCHITECTURE.md | How the plugin works (DDP + REST, multi-bot, security) |
| COMMANDS.md | Complete command reference |
| CONTRIBUTING.md | Contributors guide |