b47fcdfc14
- messaging/channels-setup.md: comprehensive guide covering all 3 channels (Telegram, Discord, iMessage), bun install, plugin setup, session persistence workarounds, and enterprise admin settings - messaging/imessage-setup.md: macOS-specific iMessage setup with Full Disk Access, /imessage access allow, and known quirks - messaging/README.md: rewritten with 3-way distinction table (Channels=event-based, Dispatch=message-based, RC=direct control) - examples/12: expanded from 2 options to 3 with clear trigger model - feature-map.md: row 9 updated to include iMessage - README.md: session persistence warning added as top-level section Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.9 KiB
Example 12: Remote Access (Three Ways)
Control your Claude Code session from your phone. Anthropic now offers three distinct ways to do this, each with a different trigger model.
OpenClaw equivalent: Telegram, WhatsApp, iMessage, or any of the 15+ messaging channels for sending commands remotely.
The three-way distinction
| Method | Trigger | Best for |
|---|---|---|
| Channels | Event-based: chat apps push messages in | Reacting to messages as they arrive |
| Dispatch | Message-based: you send a task | Delegating a job while away |
| Remote Control | Direct control: you steer the session | Guiding work in progress |
Channels = "my agent listens to a chat app" Dispatch = "I send my agent a job" Remote Control = "I take the wheel remotely"
Option A: Channels (Telegram, Discord, iMessage)
Your agent listens to a chat app and reacts to messages. The closest to OpenClaw's native channel experience.
Setup (iMessage example)
# Install plugin
/install @anthropic-ai/claude-code-imessage
# Launch with channels
claude --channels
The prompt (from your phone via iMessage)
Scrape the YouTube comments from my recent video and
give me a breakdown of the top themes and requests.
What happens
- You text the message from iMessage on your phone
- Claude Code receives it as if you typed it locally
- Claude uses your skills, tools, and API keys to execute
- The result is sent back to you via iMessage
- You can approve/deny permissions from your phone
Supported channels
- Telegram (any OS)
- Discord (any OS)
- iMessage (macOS only)
See messaging/channels-setup.md for full setup details.
Option B: Dispatch (Cowork mobile app)
Send a task from the Claude mobile app. Cowork executes on your Mac.
Setup
- Open Claude Desktop > Cowork mode
- Dispatch settings > Scan QR code with Claude mobile app
- Send a task from your phone
When to use
- You want to fire-and-forget a task
- You do not need to steer the execution
- You want Cowork features (Computer Use, connectors)
Option C: Remote Control (/rc)
Take direct control of an active CLI session from your phone or any browser.
Setup
/rc
A URL and QR code appear. Scan or open from another device.
When to use
- You want to guide an in-progress task
- You need full interactive control
- You are debugging or reviewing results live
The OpenClaw comparison
OpenClaw's 15+ native channels are always-on (daemon). All three Claude Code methods require an active session.
The biggest practical difference: If the Claude Code session closes, all remote access stops. OpenClaw keeps running. Workarounds: tmux, Mac Mini, VPS.
For most "text my agent from my phone" use cases, Channels or Dispatch gets the job done. The gap is the always-on daemon, not the phone access itself.