mirror of
https://github.com/openclaw/openclaw.git
synced 2026-02-09 05:19:32 +08:00
* feat: Make BlueBubbles the primary iMessage integration - Remove old imsg skill (skills/imsg/SKILL.md) - Create new BlueBubbles skill (skills/bluebubbles/SKILL.md) with message tool examples - Add keep-alive script documentation for VM/headless setups to docs/channels/bluebubbles.md - AppleScript that pokes Messages.app every 5 minutes - LaunchAgent configuration for automatic execution - Prevents Messages.app from going idle in VM environments - Update all documentation to prioritize BlueBubbles over legacy imsg: - Mark imsg channel as legacy throughout docs - Update README.md channel lists - Update wizard, hubs, pairing, and index docs - Update FAQ to recommend BlueBubbles for iMessage - Update RPC docs to note imsg as legacy pattern - Update Chinese documentation (zh-CN) - Replace imsg examples with generic macOS skill examples where appropriate BlueBubbles is now the recommended first-class iMessage integration, with the legacy imsg integration marked for potential future removal. * refactor: Update import paths and improve code formatting - Adjusted import paths in session-status-tool.ts, whatsapp-heartbeat.ts, and heartbeat-runner.ts for consistency. - Reformatted code for better readability by aligning and grouping related imports and function parameters. - Enhanced error messages and conditional checks for clarity in heartbeat-runner.ts. * skills: restore imsg skill and align bluebubbles skill * docs: update FAQ for clarity and formatting - Adjusted the formatting of the FAQ section to ensure consistent bullet point alignment. - No content changes were made, only formatting improvements for better readability. * style: oxfmt touched files * fix: preserve BlueBubbles developer reference (#8415) (thanks @tyler6204)
2.9 KiB
2.9 KiB
summary, read_when, title
| summary | read_when | title | ||
|---|---|---|---|---|
| Messaging platforms OpenClaw can connect to |
|
Chat Channels |
Chat Channels
OpenClaw can talk to you on any chat app you already use. Each channel connects via the Gateway. Text is supported everywhere; media and reactions vary by channel.
Supported channels
- WhatsApp — Most popular; uses Baileys and requires QR pairing.
- Telegram — Bot API via grammY; supports groups.
- Discord — Discord Bot API + Gateway; supports servers, channels, and DMs.
- Slack — Bolt SDK; workspace apps.
- Feishu — Feishu/Lark bot via WebSocket (plugin, installed separately).
- Google Chat — Google Chat API app via HTTP webhook.
- Mattermost — Bot API + WebSocket; channels, groups, DMs (plugin, installed separately).
- Signal — signal-cli; privacy-focused.
- BlueBubbles — Recommended for iMessage; uses the BlueBubbles macOS server REST API with full feature support (edit, unsend, effects, reactions, group management — edit currently broken on macOS 26 Tahoe).
- iMessage (legacy) — Legacy macOS integration via imsg CLI (deprecated, use BlueBubbles for new setups).
- Microsoft Teams — Bot Framework; enterprise support (plugin, installed separately).
- LINE — LINE Messaging API bot (plugin, installed separately).
- Nextcloud Talk — Self-hosted chat via Nextcloud Talk (plugin, installed separately).
- Matrix — Matrix protocol (plugin, installed separately).
- Nostr — Decentralized DMs via NIP-04 (plugin, installed separately).
- Tlon — Urbit-based messenger (plugin, installed separately).
- Twitch — Twitch chat via IRC connection (plugin, installed separately).
- Zalo — Zalo Bot API; Vietnam's popular messenger (plugin, installed separately).
- Zalo Personal — Zalo personal account via QR login (plugin, installed separately).
- WebChat — Gateway WebChat UI over WebSocket.
Notes
- Channels can run simultaneously; configure multiple and OpenClaw will route per chat.
- Fastest setup is usually Telegram (simple bot token). WhatsApp requires QR pairing and stores more state on disk.
- Group behavior varies by channel; see Groups.
- DM pairing and allowlists are enforced for safety; see Security.
- Telegram internals: grammY notes.
- Troubleshooting: Channel troubleshooting.
- Model providers are documented separately; see Model Providers.