2491f5c732
40 files demonstrating every major OpenClaw capability using Claude Code: - 3 agents (researcher, writer, reviewer) - 3 skills (daily-briefing, slack-message, web-research) - 2 security hooks (pre-tool-use blocker, post-tool-use logger) - 10 self-contained examples with copy-paste prompts - Complete feature map (20 capabilities, 11 full match, 7 different, 2 gap) - Security docs including NemoClaw comparison - Automation, messaging, browser, memory documentation Zero dependencies. Clone and run. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
45 lines
1.8 KiB
Markdown
45 lines
1.8 KiB
Markdown
# Messaging
|
|
|
|
How Claude Code sends and receives messages, compared to OpenClaw.
|
|
|
|
## OpenClaw: Native channel integrations
|
|
|
|
OpenClaw ships with 15+ channel connectors out of the box:
|
|
Slack, Discord, Telegram, Email, SMS, WhatsApp, and others.
|
|
Each is configured in a single YAML block. No additional setup.
|
|
|
|
## Claude Code: MCP servers + native Telegram
|
|
|
|
Claude Code uses MCP servers for most messaging channels.
|
|
Telegram is the exception: it has native support since v2.1.80.
|
|
|
|
### Native Telegram (no MCP needed)
|
|
|
|
Since v2.1.80, Claude Code has a Channels feature with Telegram support.
|
|
Since v2.1.81, permission relay allows approving tool calls from your phone.
|
|
|
|
Install the Telegram plugin in Claude Code settings, connect your account,
|
|
and Claude can send messages and wait for your approval before executing
|
|
sensitive actions - from your phone, without opening a laptop.
|
|
|
|
This is the closest to OpenClaw's native channel experience.
|
|
See `telegram-channels-setup.md`.
|
|
|
|
### MCP servers for other channels
|
|
|
|
| Channel | MCP Server | Notes |
|
|
|----------|-------------------------------|--------------------------|
|
|
| Slack | `@modelcontextprotocol/slack` | Official MCP server |
|
|
| Discord | Community MCP servers | Search MCP registry |
|
|
| Email | SMTP/IMAP MCP servers | Several available |
|
|
|
|
The `.mcp.json` in this repo includes commented examples.
|
|
See `slack-setup.md` for a complete walkthrough.
|
|
|
|
## Honest assessment
|
|
|
|
OpenClaw is easier for multi-channel messaging: install once, configure in YAML,
|
|
done. Claude Code requires setting up separate MCP servers per channel.
|
|
|
|
For single-channel use (Telegram), Claude Code's native support is now comparable.
|
|
For complex multi-channel workflows, OpenClaw has the advantage.
|