marketing-shibata50/claude-code-ultimate-guide
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: add Remote Control (§9.22) — mobile access feature documentation

Browse source 
- New section 9.22 in ultimate-guide.md with full Remote Control coverage
- Cheatsheet: dedicated section + Features Méconnues + slash commands
- security-hardening.md: Part 7 Remote Control Security threat model
- machine-readable/reference.yaml: /rc, /remote-control, /mobile, subcommand
- Resource evaluation: 2026-02-25 (score 4/5, community feedback included)

Key original content vs official Anthropic docs:
- Slash commands (/new, /compact) broken in remote UI — undocumented
- tmux multi-session workaround for 1-session limit
- Community security analysis (RCE surface, CISO implications)

Research Preview — Pro/Max plans only (v2.1.51+)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Florian BRUNIAUX 2026-02-25 18:45:41 +01:00
parent 97f9167a61
commit 5e893f3ccd
6 changed files with 527 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

34
CHANGELOG.md
View file

@ -6,6 +6,40 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
## [Unreleased]
### Added
- **Remote Control (Mobile Access) — Section 9.22** — New section in `guide/ultimate-guide.md` documenting the Remote Control feature (Research Preview, v2.1.51+, Pro/Max only)
- Two activation modes: `claude remote-control` CLI subcommand and `/rc` slash command
- QR code + session URL connection workflow, `/mobile` command for app download
- Community-sourced limitations: slash commands (`/new`, `/compact`) don't work in remote UI (undocumented in official Anthropic docs)
- Advanced patterns: tmux multi-session workaround (bypass 1-session limit), VM/cloud persistent architecture
- Security considerations, alternatives comparison (happy.engineering, OpenClaw, SSH, ngrok)
- Section 9 Recap updated with Remote Control checklist item
- TOC entry added: `[9.22 Remote Control (Mobile Access)]`
- **`guide/cheatsheet.md`** — Dedicated "Remote Control" section + Features Méconnues entry
- New section with full workflow: commands, QR/URL/app connection, limitations table, tmux pattern, auto-enable
- Added to Features Méconnues: v2.1.51 Remote Control
- CLI flags table: `remote-control` subcommand
- Slash commands table: `/remote-control`, `/rc`, `/mobile`
- **`guide/security-hardening.md`** — Part 7: Remote Control Security
- Architecture diagram (outbound-only HTTPS relay model)
- Threat model: session URL leak, RCE surface, corporate policy, persistent exposure
- Community perspective (senior dev security concerns)
- Best practices + enterprise considerations
- Comparison table: Remote Control vs SSH, ngrok, VPN+SSH
- **`machine-readable/reference.yaml`** — Remote Control entries
- Slash commands: `/remote-control`, `/rc`, `/mobile`
- CLI: `remote-control` subcommand
- Deep dive: `remote_control: 18843` line reference
- **`docs/resource-evaluations/2026-02-25-claude-code-remote-control.md`** — Resource evaluation (score 4/5)
- Full fact-check, community feedback (FR Slack), 9 press articles found
- Challenge section with risk analysis
- Original insights: slash command limitation, tmux pattern, security concerns
### Documentation
- **Claude Code Releases**: Updated tracking to v2.1.56 (v2.1.52 → v2.1.56)

209
docs/resource-evaluations/2026-02-25-claude-code-remote-control.md Normal file
View file

@ -0,0 +1,209 @@
# Resource Evaluation: Claude Code Remote Control
**Date**: 2026-02-25
**Evaluator**: Claude (claude-sonnet-4-6)
**Status**: Completed
---
## Metadata
| Field | Value |
|-------|-------|
| **URL** | https://code.claude.com/docs/en/remote-control |
| **Type** | Official Anthropic documentation + feature announcement |
| **Date** | 2026-02-25 |
| **Score** | 4/5 |
| **Decision** | Integrate this week |
---
## 1. Content Summary
Remote Control allows continuing a local Claude Code session from a phone, tablet, or web browser (claude.ai/code or Claude mobile app on iOS/Android).
**Two activation modes:**
- `claude remote-control` — new CLI subcommand
- `/remote-control` or `/rc` — slash command from an active session
**Key architecture:**
- Execution is 100% local — the terminal does all the work
- Mobile/web interface is a remote window onto the local session
- HTTPS outbound only, zero inbound ports, short-lived scoped credentials
**Availability:** Research Preview on Pro and Max plans. NOT available on Team, Enterprise, or API keys.
**Features:** QR code + session URL for fast connection, auto-enable via `/config`, `/mobile` command for app download links.
**Limitations:** 1 remote session at a time, terminal must stay open, ~10min network timeout.
---
## 2. Relevance Score
**Score: 4/5 — Very Relevant (significant improvement)**
| Score | Meaning |
|-------|---------|
| 5 | Essential — Major gap in the guide |
| **4** | **Very relevant — Significant improvement** |
| 3 | Relevant — Useful complement |
| 2 | Marginal — Secondary info |
| 1 | Out of scope — Not relevant |
**Justification:**
- Feature entirely new, zero coverage in ultimate-guide.md
- Partially tracked in releases tracker (v2.1.51 and v2.1.53)
- Introduces a new access paradigm (local execution + remote UI)
- HOWEVER: research preview (not GA), limited Pro/Max scope, potentially unstable API
---
## 3. Gap Analysis
| Aspect | Doc officielle Anthropic | Notre guide |
|--------|--------------------------|-------------|
| Remote Control feature | Complete detailed doc | Zero mention in ultimate-guide.md |
| `claude remote-control` command | Documented with flags | Missing from cheatsheet |
| `/rc` and `/remote-control` slash commands | Documented | Missing |
| Security model | Detailed (HTTPS outbound, credentials) | Not covered |
| Difference vs "Claude Code on the Web" | Clear comparison table | Not covered |
| QR code + session URL | Detailed workflow | Not covered |
| Config auto-enable | Via `/config` | Not covered |
| Releases tracker | v2.1.51 and v2.1.53 | Already up to date |
| `/mobile` command | Mentioned | Missing from guide |
---
## 4. Integration Recommendations
### Files to modify
| File | Action | Priority |
|------|--------|----------|
| `guide/ultimate-guide.md` | New section 9.22 "Remote Control" | High |
| `guide/cheatsheet.md` | Add `/remote-control`, `/rc`, `/mobile` to command table | High |
| `machine-readable/reference.yaml` | Add `remote-control` entry with target line | High |
| `guide/security-hardening.md` | Note on security implications of remote access | Medium |
### Content to document
1. **What is Remote Control** — definition, difference vs "Claude Code on the Web" and vs Teleportation
2. **Setup** — requirements (Pro/Max, /login, workspace trust)
3. **Two workflows** — `claude remote-control` (CLI) vs `/rc` (from session)
4. **Connection** — QR code, URL, mobile app, session list
5. **Config** — auto-enable via `/config`
6. **Security** — outbound-only model, scoped credentials
7. **Limitations** — 1 session, terminal open, 10min timeout, **slash commands don't work in remote UI**
8. **Disclaimer** — Research Preview clearly noted
---
## 5. Challenge (Technical Review)
**Score adjusted: 4/5** (down from 5)
**Reasons for downgrade:**
- Research preview, not GA → risk of documenting content that changes
- Restricted Pro/Max scope → majority of pro users (Team/Enterprise) don't have access
- Official Anthropic docs already accessible → guide isn't first source for early adopters
**Points missed in initial eval:**
- Distinction between CLI workflow (`claude remote-control` with `--verbose`, `--sandbox` flags) vs slash command (`/rc` without flags)
- Impact for enterprise environments with proxy/VPN/restrictive firewall
- `/mobile` command to download Claude app (mentioned in doc, not in our guide)
- Comparison with existing alternatives (SSH + mobile terminal, tmux, VS Code remote)
**Non-integration risks:**
- Short term (1-2 weeks): low, early adopters read Anthropic docs
- Medium term (1 month): moderate if feature goes GA
- Long term: high if remote-control becomes standard interaction mode
**Main risk: over-documenting an unstable preview** → solution: document with clear "Research Preview" disclaimer
---
## 6. Fact-Check
| Claim | Verified | Source |
|-------|----------|--------|
| Available on Pro and Max | ✅ | Official doc + Perplexity (multiple sources) |
| Research preview | ✅ | Official doc ("research preview") |
| Not Team/Enterprise | ✅ | Official doc ("not available on Team or Enterprise") |
| HTTPS outbound only | ✅ | Official doc ("never opens inbound ports") |
| Timeout ~10 min | ✅ | Official doc ("more than roughly 10 minutes") |
| v2.1.51 first mention | ✅ | claude-code-releases.yaml line 47 |
| `/rc` alias for `/remote-control` | ✅ | Official doc |
| QR code via spacebar | ✅ | Official doc ("press spacebar to show a QR code") |
| Claude app iOS + Android | ✅ | Official doc (App Store + Play Store links) |
| "$2.5B annualized revenue" (Perplexity) | ❌ Not verifiable | MLQ.ai article claim, not in official doc. Ignored. |
| "29M daily VS Code installations" (Perplexity) | ❌ Not verifiable | Article claim, not in official doc. Ignored. |
---
## 7. Community Articles Found
| Source | Title | Date | Type |
|--------|-------|------|------|
| HelpNetSecurity | "Anthropic's Remote Control feature brings Claude Code to mobile" | 2026-02-25 | Press article |
| TechRadar | "Anthropic reveals Remote Control, a mobile version of Claude Code" | 2026-02-25 | Press article |
| MLQ.ai | "Anthropic Launches Remote Control Feature for Claude Code" | 2026-02-25 | Tech article |
| AwesomeAgents.ai | "Claude Code Gets Remote Control" | 2026-02-24 | Tech article |
| YouTube | "RIP OpenClaw!? This New Claude Code Feature is CRAZY!" | 2026-02-25 | Video |
| YouTube | "Claude Code Just Destroyed OpenClaw (new /remote-control)" | 2026-02-24 | Video |
| Binance Square | "Claude Code Introduces Remote Control Feature for Max Users" | 2026-02-25 | News |
**Observations:** Significant community buzz. Several articles compare to OpenClaw (open-source alternative that Remote Control may make obsolete). Significant press coverage for a preview feature.
---
## 8. Community Feedback (FR Slack, 2026-02-25)
Source: French-speaking developer Slack discussion (~15 messages, 7 participants)
### Field Insights (Not in Official Docs)
| Observation | Impact on guide |
|-------------|-----------------|
| Bash/AskUserQuestion permissions appear on the phone | Document: mobile serves as an approval terminal |
| Slash commands (`/new`, `/compact`) DON'T WORK in remote — treated as plain text | **Major limitation missing from official docs** |
| Skills ARE loaded on demand in remote | Positive: skills work |
| Works on remote VM (Clever Cloud) in tmux | Advanced use case to document |
| Multi-session workaround: multiple tmux tabs, each with own claude session | Pattern to document (bypasses single-session limit) |
| Server setup: 6-8 Claude sessions in tmux, no interruption while traveling | Advanced architecture to document |
| happy.engineering = main open-source alternative now "obsolete" | Mention in comparison |
### Security Concerns (Senior Devs)
| Concern | Analysis |
|---------|----------|
| "C'est une sacree RCE qu'ils introduisent là" (Frédéric C.) | True: session URL = live access key to local terminal. Real attack surface. |
| "Mon CISO va bientôt me challenger" (Mat F.) | Enterprise implication: even on personal plan, if used on corporate machine |
| Per-command permissions limit risk but "an attacker would say yes to everything" | Valid nuance: mobile approval guards against unintentional actions, not active attacker |
| Suggestion: use on "hardened trusted workstation à la Chromebook" | Best practice to document |
### Overall Sentiment
- **Strong enthusiasm**: "KILLER FEATURE", "finally", "here it is"
- **Immediate adoption**: several tested it within hours of announcement
- **Alternatives made obsolete**: happy.engineering, SSH/VPS hacks, OpenClaw
- **Perceived maturity**: "quite limited for now" (Hubert), single-session, no slash commands
- **Adoption score**: 8/10 (enthusiasm) but 5/10 (current maturity)
---
## 9. Final Decision
- **Final score**: 4/5
- **Action**: Integrate this week with "Research Preview" disclaimer
- **Confidence**: High (official doc verified, community feedback confirmed, multiple press sources)
### Added Value vs Official Doc
Thanks to community feedback, the guide can provide **original content** not in Anthropic docs:
1. **Slash commands limitation in remote** (`/new`, `/compact` treated as text) — undocumented
2. **tmux multi-session pattern** to bypass single-session limit
3. **Permanent server architecture**: tmux + remote VM + remote-control
4. **Community security analysis**: RCE surface, CISO implications, best practices (hardened workstation)
5. **Alternatives comparison**: happy.engineering, OpenClaw, SSH tunnels, VPS setups

42
guide/cheatsheet.md
View file

@ -32,6 +32,9 @@ tags: [cheatsheet, reference]
| `/teleport` | Teleport session from web |
| `/tasks` | Monitor background tasks |
| `/remote-env` | Configure cloud environment |
| `/remote-control` | Start remote control session (Research Preview, Pro/Max) |
| `/rc` | Alias for /remote-control |
| `/mobile` | Get Claude mobile app download links |
| `/fast` | Toggle fast mode (2.5x speed, 6x cost) |
| `/debug` | Systematic troubleshooting |
| `/exit` | Quit (or Ctrl+D) |
@ -80,6 +83,7 @@ tags: [cheatsheet, reference]
| **Auto-Memories** | v2.1.32 | Automatic cross-session context capture |
| **Session Forking** | v2.1.19 | Rewind + create parallel timeline |
| **LSP Tool** | v2.0.74 | Code intelligence (go-to-def, refs) |
| **Remote Control** | v2.1.51 | Control local session from phone/browser (Research Preview, Pro/Max) |
**Pro tip**: These aren't "secrets"—they're in the [CHANGELOG](https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md). Read it!
@ -381,6 +385,7 @@ VERIFY: Empty email shows error, invalid format shows error
| `-c` / `--continue` | Continue last session |
| `-r` / `--resume <id>` | Resume specific session |
| `--teleport` | Teleport session from web |
| `remote-control` | Subcommand: start remote control session |
| `--model sonnet` | Change model |
| `--add-dir ../lib` | Allow access outside CWD |
| `--permission-mode plan` | Plan mode |
@ -422,6 +427,43 @@ claude -p "fix typos" --dangerously-skip-permissions
---
## Remote Control — Mobile Access (v2.1.51+, Research Preview)
> **Pro/Max only** — not available on Team, Enterprise, or API keys
```bash
# Start from terminal (new session)
claude remote-control
# Or from inside an active session:
/rc # (or /remote-control)
```
**Connect from phone/tablet/browser:**
1. Scan the **QR code** (press spacebar after start)
2. Or open **session URL** in browser / Claude mobile app
3. Or: `/mobile` → shows App Store + Play Store links
| ⚠️ Known Limitation | Detail |
|--------------------|--------|
| 1 session at a time | Only one remote session active |
| Slash commands broken | `/new`, `/compact` = plain text remotely → use from local terminal |
| Terminal must stay open | Closing local terminal ends session |
| Network timeout | ~10 min disconnect → session expires |
**Advanced: tmux multi-session** (bypass 1-session limit)
```bash
tmux new-session -s dev
# Each pane = its own claude session
# Run /rc in the pane you want to control remotely
```
**Auto-enable:** `/config` → toggle "Remote Control: auto-enable"
**Full doc**: [§9.22 Remote Control](ultimate-guide.md#922-remote-control-mobile-access) | [Security notes](security-hardening.md#remote-control-security)
---
## Task Management (v2.1.16+)
**Two systems available:**

72
guide/security-hardening.md
View file

@ -833,4 +833,74 @@ Beyond securing Claude Code itself, Anthropic offers a dedicated vulnerability s
---
*Version 1.1.0 | February 2026 | Part of [Claude Code Ultimate Guide](../README.md)*
## Part 7: Remote Control Security {#remote-control-security}
> **Feature context**: Remote Control (Research Preview, Feb 2026) allows controlling a local Claude Code session from a phone, tablet, or browser. Available on Pro and Max plans only.
### Architecture
```
Local terminal ──HTTPS outbound──► Anthropic relay ──► Mobile/Browser
(execution) (relay only) (control UI)
```
**Security properties:**
- Zero inbound ports (reduces attack surface vs SSH tunnels or ngrok)
- HTTPS only (encrypted in transit)
- Session URL = short-lived authentication token
- Execution stays 100% local
### Threat Model
| Threat | Risk | Mitigation |
|--------|------|------------|
| **Session URL leak** | Full terminal access for whoever holds the URL | Treat URL as password — don't share in Slack/logs/screenshots |
| **RCE via remote commands** | Attacker who gets the URL can run commands if they approve tool calls | Per-command approval prompts on mobile (not foolproof against active attacker) |
| **Corporate policy violation** | Personal Claude account on corporate machine routes traffic through Anthropic relay | Verify policy before enabling, even on personal plans |
| **Persistent session exposure** | Long-running sessions increase window of exposure | Close sessions when done; ~10min auto-timeout on disconnect |
| **Shared/untrusted workstation** | Session URL valid while session is open | Never run remote-control on shared machines |
> **Community perspective**: Senior devs immediately noted: "C'est une sacrée RCE qu'ils introduisent là." The session URL is effectively a live key to an executing terminal. The per-command approval mechanism limits accidental execution but does not protect against a determined attacker who holds the URL and approves all prompts.
### Best Practices
```bash
# 1. Don't auto-enable — activate only when needed
# Avoid: /config → auto-enable remote-control
# 2. Use on a dedicated, hardened workstation
# Not on machines with access to production credentials or secrets
# 3. Close the session when done
# Ctrl+C on local terminal, or dismiss from the mobile app
# 4. Never share session URLs in team chats, tickets, or logs
# They are live access tokens while the session is active
# 5. Prefer use on personal dev machines
# Not on corporate machines with elevated privileges
```
### Enterprise Considerations
Remote Control is **not available** on Team or Enterprise plans. However:
- Developers on personal Pro/Max accounts may use it on corporate hardware
- The relay traffic (your commands and Claude's responses) passes through Anthropic infrastructure
- If your organization has strict data residency requirements, treat Remote Control like any cloud-routed tool
- Recommended: use only on a dedicated "sandbox" workstation without access to production systems
### Comparison: Remote Control vs Alternatives
| Method | Inbound ports | Data path | Risk level |
|--------|---------------|-----------|------------|
| **Remote Control** | None (outbound HTTPS) | Anthropic relay | Low-Medium |
| **SSH + mobile terminal** | Yes (port 22) | Direct | Medium |
| **ngrok tunnel** | None (outbound) | ngrok relay | Medium |
| **VPN + SSH** | Yes (behind VPN) | VPN + direct | Low |
For the highest security: prefer SSH over VPN rather than Remote Control, especially on sensitive environments.
---
*Version 1.2.0 | February 2026 | Part of [Claude Code Ultimate Guide](../README.md)*

166
guide/ultimate-guide.md
View file

@ -186,6 +186,7 @@ Context full → /compact or /clear
- [9.19 Permutation Frameworks](#919-permutation-frameworks)
- [9.20 Agent Teams (Multi-Agent Coordination)](#920-agent-teams-multi-agent-coordination)
- [9.21 Legacy Codebase Modernization](#921-legacy-codebase-modernization)
- [9.22 Remote Control (Mobile Access)](#922-remote-control-mobile-access)
- [10. Reference](#10-reference)
- [10.1 Commands Table](#101-commands-table)
- [10.2 Keyboard Shortcuts](#102-keyboard-shortcuts)
@ -18768,6 +18769,170 @@ The average gains are real and significant. The headline numbers require favorab
---
## 9.22 Remote Control (Mobile Access)
**Reading time**: 7 minutes
**Skill level**: Week 2+
**Status**: Research Preview (as of February 2026)
**Availability**: Pro and Max plans only — not available on Team, Enterprise, or API keys
Remote Control lets you monitor and control a local Claude Code session from a phone, tablet, or web browser — without migrating anything to the cloud. Your terminal keeps running locally; the mobile/web interface is a remote window onto that session.
> **Key difference from Session Teleportation (§9.16)**: Teleportation *migrates* a session (web → local). Remote Control *mirrors* a local session to a remote viewer. Execution always stays on your local machine.
### How It Works
```
Local terminal (running claude)
│
│ HTTPS outbound only (no inbound ports)
▼
Anthropic relay
│
▼
Phone / tablet / browser (claude.ai/code or Claude app)
```
- **Execution**: 100% local — your terminal does all the work
- **Security**: HTTPS outbound only, zero inbound ports, short-lived scoped credentials
- **What you can do remotely**: Send messages, approve/deny tool calls, read responses
### Setup
**Requirements:**
- Claude Code v2.1.51+
- Active Pro or Max subscription (not Team/Enterprise)
- Logged in (`/login`)
### Two Ways to Start
**Option A — From the command line (start a new session):**
```bash
claude remote-control
# Optional flags:
# --verbose Show detailed connection logs
# --sandbox Restrict to sandbox mode
```
**Option B — From inside an active session:**
```
/remote-control
# or the shorter alias:
/rc
```
### Connecting from Your Device
Once started, Claude Code displays:
1. A **session URL** (open in any browser)
2. Press **spacebar** to show a **QR code** (scan with your phone)
3. Or open the **Claude app** (iOS / Android) — your active session appears automatically
To enable remote control on every session by default:
```
/config → toggle "Remote Control: auto-enable"
```
### Download the Mobile App
```
/mobile # Shows App Store + Google Play download links
```
### Known Limitations (Research Preview)
| Limitation | Detail |
|------------|--------|
| **1 session at a time** | Only one active remote control session |
| **Terminal must stay open** | Closing the local terminal ends the session |
| **Network timeout** | ~10 min before session expires on disconnect |
| **Slash commands don't work remotely** | `/new`, `/compact`, etc. are treated as plain text in the remote UI |
| **Pro/Max only** | Not available on Team, Enterprise, or API keys |
> **⚠️ Slash commands limitation**: When you type `/new`, `/compact`, or any slash command in the remote interface (mobile app or browser), they are treated as plain text messages — not forwarded as commands to the local CLI. Use slash commands from your local terminal instead.
### Advanced Patterns (Community-Validated)
#### Multi-Session via tmux (Workaround for 1-Session Limit)
```bash
# Start a tmux session with multiple panes
tmux new-session -s dev
# Each tmux pane can run its own claude session:
# Pane 1: claude → run /rc → share URL with your phone
# Pane 2: claude (local only)
# Pane 3: claude (local only)
# To switch which session you're controlling remotely:
# → Go to pane 2, run /rc (disconnects pane 1's remote, connects pane 2)
```
Each tmux pane hosts its own Claude session. Only one can use remote-control at a time, but you can switch between sessions by running `/rc` in different panes.
#### Persistent Server Architecture (VM/Cloud)
Remote Control works on remote machines (VMs, cloud servers) running in tmux:
```bash
# On your cloud server (e.g., Clever Cloud, AWS, etc.):
tmux new-session -s claude-server
claude remote-control
# → Scan QR code from your phone
# → Control a cloud-hosted Claude session from mobile
# → Sessions survive laptop reboots (tmux keeps them alive)
```
This gives you persistent sessions that survive closing your laptop. Combine 6-8 Claude sessions in tmux for continuous uninterrupted work while traveling.
### Alternatives (Pre-Remote Control)
| Alternative | How it worked | Status |
|-------------|---------------|--------|
| [happy.engineering](https://happy.engineering) | Open-source remote access for Claude Code | Community-declared obsolete post-RC |
| OpenClaw | Alternative Claude Code remote interface | Community-declared obsolete post-RC |
| SSH + mobile terminal | SSH into dev machine, run claude | Still valid for Team/Enterprise users |
| VS Code Remote | Remote SSH extension + Claude Code | Still valid, more complex setup |
### Security Considerations
> **Full threat model**: [Security Hardening Guide: Remote Control Security](./security-hardening.md#remote-control-security)
**Quick summary:**
- The session URL is a **live access key** — treat it like a password
- Anyone with the URL can send commands to your local Claude session while active
- Short-lived credentials + HTTPS outbound-only limits the exposure window
- Per-command approval prompts on mobile guard against accidental execution (not against active attackers)
- **Not recommended** on shared or untrusted workstations
- Corporate machines: verify your security policy even on personal Pro/Max accounts
### Troubleshooting
| Issue | Solution |
|-------|----------|
| Session not appearing on phone | Ensure same Claude account, refresh app |
| QR code not showing | Press spacebar after starting remote-control |
| Slash commands not working | Type them in your local terminal instead |
| Session expired | Reconnect: run `/rc` again |
| Corporate firewall blocking | HTTPS outbound (port 443) must be allowed |
| "Not available" error | Verify Pro or Max subscription (not Team/Enterprise) |
### Evolution Timeline
| Version | Feature |
|---------|---------|
| **2.1.51** | Initial Remote Control feature (Research Preview) |
| **2.1.53** | Stability improvements and bug fixes |
---
## 🎯 Section 9 Recap: Pattern Mastery Checklist
Before moving to Section 10 (Reference), verify you understand:
@ -18797,6 +18962,7 @@ Before moving to Section 10 (Reference), verify you understand:
**Advanced Workflows**:
- [ ] **Session Teleportation**: Migrate sessions between cloud and local environments
- [ ] **Remote Control**: Monitor/control local sessions from mobile or browser (Research Preview, Pro/Max)
- [ ] **Background Tasks**: Run tasks in cloud while working locally (`%` prefix)
- [ ] **Multi-Instance Scaling**: Understand when/how to orchestrate parallel Claude instances (advanced teams only)
- [ ] **Agent Teams**: Multi-agent coordination for read-heavy tasks (experimental, Opus 4.6+)

5
machine-readable/reference.yaml
View file

@ -602,6 +602,7 @@ deep_dive:
git_best_practices: 8412
cost_optimization: 8878
session_teleportation: 9477
remote_control: 18843
multi_instance_workflows: 9583
boris_cherny_case_study: 9617
boris_cherny_team_patterns: 11822
@ -958,6 +959,9 @@ commands:
/teleport: "bring web session to local CLI"
/tasks: "monitor background tasks"
/remote-env: "configure cloud environment"
/remote-control: "start remote control session (Research Preview, Pro/Max only)"
/rc: "alias for /remote-control"
/mobile: "get Claude mobile app download links (iOS + Android)"
# ════════════════════════════════════════════════════════════════
# SHORTCUTS - see deep_dive.shortcuts_table
@ -978,6 +982,7 @@ cli:
"-c": "continue last session"
"-r <id>": "resume specific session"
"--teleport": "bring web session to local CLI"
"remote-control": "subcommand: start remote control session"
"-p": "non-interactive (pipe mode)"
"--model X": "select model"
"--dangerously-skip-permissions": "auto-accept ALL (danger)"