0d0b83f98c
Add three new sections to all 14 examples: - "Carry Forward": what output feeds into later examples (01-10) - "The Cumulative Path": alternative prompt building on previous output (02-10) - "Now Try It Yourself": personalized template with transferable pattern (all) - "Building On" callout connecting back to previous examples (02-10) Add Example 14: Build Your Personal Agent - capstone that guides reader through writing their own CLAUDE.md, creating a personal skill, connecting a messaging channel, setting up automation, and testing end-to-end. Update README with cumulative path diagram, two usage modes, and example 14. Update GETTING-STARTED.md with cross-references to relevant examples. 17 files changed, 703+ lines added. The examples now form a coherent learning path from "see what it can do" to "build your own agent." Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
3.8 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.
Now Try It Yourself
Pick the method that fits how you work:
If you want "text my agent" (Channels):
[From your phone via iMessage/Telegram/Discord]
Run /weekly-status and send me the summary.
If you want "fire and forget" (Dispatch): Open Claude Desktop > Cowork > Dispatch. Send a task from your phone.
If you want "take the wheel" (Remote Control):
/rc
Scan the QR code from your phone. You now have full control.
The pattern you just learned: three access methods for three use cases. Channels for reactive messaging, Dispatch for delegated tasks, Remote Control for interactive steering. Most people start with one and add others as needed.
Ideas worth trying:
- Text "morning briefing" from bed and get a summary before coffee
- Dispatch "prepare the meeting notes for today" while commuting
- Use /rc to guide Claude through a debugging session from your couch