feat: initial companion repo for OpenClaw vs Claude Code article

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>

messaging/README.md

@@ -0,0 +1,45 @@
+# 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.

messaging/slack-setup.md

@@ -0,0 +1,56 @@
+# Slack Setup via MCP
+
+## 1. Create a Slack App
+
+Go to https://api.slack.com/apps and click "Create New App".
+Choose "From scratch". Give it a name and select your workspace.
+
+## 2. Add Bot Token Scopes
+
+Navigate to "OAuth & Permissions" in the sidebar.
+Under "Bot Token Scopes", add:
+- `chat:write` - post messages
+- `channels:read` - list channels
+- `channels:history` - read messages (if needed)
+
+## 3. Install to workspace
+
+Click "Install to Workspace" at the top of the OAuth & Permissions page.
+Authorize. Copy the "Bot User OAuth Token" (starts with `xoxb-`).
+
+## 4. Add to .mcp.json
+
+```json
+{
+  "mcpServers": {
+    "slack": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-slack"],
+      "env": {
+        "SLACK_BOT_TOKEN": "xoxb-your-token-here",
+        "SLACK_TEAM_ID": "T0123456789"
+      }
+    }
+  }
+}
+```
+
+Find your Team ID in the Slack URL when logged into the web app:
+`https://app.slack.com/client/T0123456789/...`
+
+Store the token in an environment variable rather than hardcoding it.
+
+## 5. Test
+
+Start Claude Code in your project directory. Try:
+
+```
+Send a message to #general saying "Claude Code Slack integration is working"
+```
+
+Claude will use the `slack_post_message` tool from the MCP server.
+
+## Troubleshooting
+
+- "not_in_channel": Invite the bot to the channel first (`/invite @your-bot-name`)
+- Token not found: verify the env var is exported before launching Claude Code

messaging/telegram-channels-setup.md

@@ -0,0 +1,41 @@
+# Telegram Channels Setup
+
+Native Telegram support was added in Claude Code v2.1.80. No MCP server needed.
+
+## What you get
+
+- **v2.1.80+**: Claude Code can send messages to Telegram
+- **v2.1.81+**: Permission relay - Claude pauses on sensitive actions and sends
+  you an approval request on Telegram. You approve or deny from your phone.
+
+This is the closest Claude Code equivalent to OpenClaw's native channel integrations.
+
+## Setup
+
+1. Open Claude Code settings (gear icon or `/config`)
+2. Navigate to Channels or Integrations
+3. Select Telegram and click Connect
+4. A Telegram bot will send you a link or code to authorize
+5. Complete authorization in the Telegram app
+
+## Usage
+
+Once connected, Claude Code can:
+
+```
+Send me a Telegram message when the build finishes
+```
+
+```
+Ask for my approval before deleting any files
+```
+
+For permission relay specifically, Claude will send a message like:
+"I'm about to run `rm -rf ./dist`. Approve? [Yes] [No]"
+You tap Yes or No. Claude proceeds or stops based on your response.
+
+## Note on MCP alternative
+
+If you need Telegram features not covered by the native integration,
+the `telegram-bot-api` MCP server is available as a fallback.
+For most use cases, the native integration is sufficient and simpler.