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/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.