Desktop, Web & Remote Control

Every surface runs the same Claude Code engine — CLAUDE.md, settings, and MCP servers carry across. This file covers working beyond the terminal and moving sessions between devices.

Desktop App

Standalone app (macOS, Windows, Linux beta). Strengths over the CLI:

• Visual diff review side by side
• Parallel sessions in one window, each in its own auto-created worktree
• Scheduled tasks that run locally with full file access
• Cloud sessions — kick off work on Anthropic-managed VMs
• Computer use — let Claude control apps on your screen
• Dispatch — message a task from your phone; open the resulting session on Desktop

Hand off a terminal session to Desktop anytime with /desktop.

Claude Code on the Web (claude.ai/code)

Zero local setup; runs in a cloud sandbox cloned from GitHub. Ideal for:

• Long-running tasks you check on later
• Repos you don’t have locally
• Parallel independent tasks
• Working from the iOS app

Teleport — pull cloud work into your terminal

claude --teleport            # pick a web/mobile session, continue locally

Start on the phone during a commute, finish at your desk with full local tooling. (Requires a claude.ai subscription.)

Remote Control

The reverse direction: your local session keeps running on your machine, and you drive it from claude.ai or the Claude mobile app.

/remote-control      # or: claude --remote-control

Copy the link / scan the QR, then steer the session from your phone: reply to prompts, approve permissions, send follow-ups. Great for kicking off a long task and answering its questions from the couch.

Which One When?

Situation	Use
Review diffs visually, run parallel local sessions	Desktop
Task on a repo you don’t have locally	Web
Started locally, need to leave the desk	Remote Control
Started on web/mobile, now at your desk	claude --teleport
Fire a task from your phone, pick up on Desktop later	Dispatch
Trigger events into a running session from chat apps	Channels (39-slack-chrome-channels.md)

Deep Links

Launch pre-configured sessions from URLs (claude.ai/code links with repo + prompt) — useful for runbooks and issue templates: see https://code.claude.com/docs/en/deep-links

Real Case: The Commute Workflow

07:40  (train, phone)  Open Claude iOS → claude.ai/code →
       "Investigate issue #88 — memory leak in the worker pool.
        Write findings to FINDINGS.md and draft a fix."
08:30  (desk)          claude --teleport → select the session
       Full local tools now: run the profiler, verify the fix, commit.
12:00  (lunch)         Kick off refactor locally → /remote-control
       Approve its two permission prompts from your phone while eating.

🧠 Quick Recall

• Trick: “Teleport pulls work in; Remote Control reaches out.”
• Phone → desk: teleport. Desk → phone: remote control.

👨‍🏫 Teach It

• Show: approve a permission prompt from your phone, held up for the room.
• They’ll trip on: teleport needs a claude.ai subscription.

---

Learning path: ⬅ 37-vs-code-extension.md · Index · ➡ 39-slack-chrome-channels.md