feat: add iMessage channel, channels setup guide, 3-way distinction
- 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>
This commit is contained in:
Kjell Tore Guttormsen
parent
e8a5403f91
commit
b47fcdfc14
6 changed files with 355 additions and 77 deletions
|
|
@ -1,71 +1,115 @@
|
|||
# Example 12: Remote Control and Dispatch
|
||||
# Example 12: Remote Access (Three Ways)
|
||||
|
||||
Control your Claude Code session from your phone. This is
|
||||
Anthropic's answer to OpenClaw's Telegram integration: manage
|
||||
your AI agent from anywhere.
|
||||
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, or any of the
|
||||
15+ messaging channels for sending commands remotely.
|
||||
**OpenClaw equivalent:** Telegram, WhatsApp, iMessage, or any
|
||||
of the 15+ messaging channels for sending commands remotely.
|
||||
|
||||
## Option A: Remote Control (/rc) for Claude Code
|
||||
## The three-way distinction
|
||||
|
||||
Works with the CLI. No Cowork needed.
|
||||
| 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 |
|
||||
|
||||
### Setup
|
||||
**Channels** = "my agent listens to a chat app"
|
||||
**Dispatch** = "I send my agent a job"
|
||||
**Remote Control** = "I take the wheel remotely"
|
||||
|
||||
1. Start a Claude Code session in your terminal
|
||||
2. Type `/rc` (short for `/remote-control`)
|
||||
3. A URL and QR code appear
|
||||
4. Scan the QR code with your phone or open the URL in any browser
|
||||
5. You now have a full interactive session from your phone
|
||||
---
|
||||
|
||||
### The prompt (from your phone)
|
||||
## 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)
|
||||
|
||||
```bash
|
||||
# Install plugin
|
||||
/install @anthropic-ai/claude-code-imessage
|
||||
|
||||
# Launch with channels
|
||||
claude --channels
|
||||
```
|
||||
|
||||
### The prompt (from your phone via iMessage)
|
||||
|
||||
```
|
||||
Search the web for the latest Claude Code changelog entries,
|
||||
summarize the 3 most important features, and save the summary
|
||||
to changelog-latest.md in the project root.
|
||||
Scrape the YouTube comments from my recent video and
|
||||
give me a breakdown of the top themes and requests.
|
||||
```
|
||||
|
||||
### What happens
|
||||
|
||||
- Your phone sends the message to the active CC session
|
||||
- Claude Code executes on your computer (terminal stays active)
|
||||
- Results appear on both your phone and the terminal
|
||||
- You can continue the conversation from either device
|
||||
1. You text the message from iMessage on your phone
|
||||
2. Claude Code receives it as if you typed it locally
|
||||
3. Claude uses your skills, tools, and API keys to execute
|
||||
4. The result is sent back to you via iMessage
|
||||
5. You can approve/deny permissions from your phone
|
||||
|
||||
## Option B: Dispatch for Cowork
|
||||
### Supported channels
|
||||
|
||||
If you use Claude Cowork (desktop app), Dispatch lets you
|
||||
assign tasks from the Claude mobile app.
|
||||
- **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
|
||||
|
||||
1. Open Claude Desktop app on Mac
|
||||
2. Switch to Cowork mode
|
||||
3. Go to Dispatch in settings
|
||||
4. Scan QR code with Claude mobile app (iOS/Android)
|
||||
5. Your phone is now paired to your desktop agent
|
||||
1. Open Claude Desktop > Cowork mode
|
||||
2. Dispatch settings > Scan QR code with Claude mobile app
|
||||
3. Send a task from your phone
|
||||
|
||||
### How it differs from /rc
|
||||
### When to use
|
||||
|
||||
| Feature | /rc (Claude Code) | Dispatch (Cowork) |
|
||||
|---------|------------------|------------------|
|
||||
| Interface | Terminal session | Desktop app |
|
||||
| Requires | CLI | Cowork desktop app |
|
||||
| Phone app | Any browser | Claude mobile app |
|
||||
| Computer Use | No | Yes |
|
||||
| Connected apps | Via MCP | Built-in (Slack, Google, Notion) |
|
||||
- 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 lets you text your agent via Telegram, WhatsApp,
|
||||
Discord, or 12+ other channels. The agent is always-on.
|
||||
OpenClaw's 15+ native channels are always-on (daemon). All
|
||||
three Claude Code methods require an active session.
|
||||
|
||||
Claude Code /rc requires an active session. Dispatch requires
|
||||
Cowork running on your Mac. Neither is truly "always-on" in
|
||||
the OpenClaw sense, but /schedule (remote triggers) can start
|
||||
sessions on demand from the web.
|
||||
**The biggest practical difference:** If the Claude Code
|
||||
session closes, all remote access stops. OpenClaw keeps
|
||||
running. Workarounds: tmux, Mac Mini, VPS.
|
||||
|
||||
The gap is narrowing. For most "text my agent from my phone"
|
||||
use cases, /rc or Dispatch gets the job done.
|
||||
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.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue