Part I — Claude Code away from your laptop: Desktop, mobile, and the browser

Everything so far assumes you're sitting at your laptop with a terminal open. Claude Code also has a full Desktop app, works from your phone, and can even run coding sessions entirely in the cloud from a browser — useful once you want to check on a task from the couch, or kick one off without opening your laptop at all.

I1. The Desktop app — more than just a terminal in a window

Download it from claude.ai (Mac, Windows, and a Linux beta are all supported). It has three tabs:

• Chat — ordinary conversations, like the website.
• Code — the same Claude Code you've been using in the terminal, with a graphical layer on top:
  • Multiple sessions in parallel, each isolated in its own Git worktree, so working on two things at once never lets one session's changes bleed into another's.
  • Side-by-side panes so you can watch two sessions at once.
  • Visual diff review before changes are applied — see exactly what's about to change, not just trust the terminal output.
  • Connectors — one-click integrations (Google Calendar, Slack, GitHub, Linear, Notion, and more) that Claude can read from and act on mid-session.
  • Computer use (optional) — Claude can see and control other apps on your desktop directly (clicking, typing, taking screenshots), with three permission tiers depending on the app: view-only (browsers), click-only (terminals/IDEs), or full control. You approve each app the first time Claude touches it.
• Cowork — a more open-ended, longer-running assistant (project research, documents, spreadsheets) separate from coding work, and the tab that Dispatch (below) lives in.

I2. What the phone app can actually do

The free Claude app (iOS and Android) covers ordinary chat — voice input, camera photos, file sharing from other apps, and (on iOS) Siri Shortcuts. On its own, the phone app cannot run Claude Code the way your laptop can — there's no local filesystem, no terminal, nowhere for a coding agent to actually execute commands or edit files.

What it can do for development work is act as a window into a coding session running somewhere else — either your own machine, or a cloud sandbox. That's the "overcoming the limitation" part, and there are two real ways to do it.

I3. Two ways to code from your phone (and how they differ)

Both are reachable from any browser (including your phone's) at claude.ai/code, or from the Code tab of the Claude mobile app.

I4. Remote Control — the closest thing to "full Claude Code" on your phone

Since Remote Control runs on your actual machine, it has your actual filesystem, your actual MCP servers, and — unlike a cloud sandbox — no limitations beyond what your terminal itself can do. This is genuinely full Claude Code; your phone is just a window into it.

To start it, from a terminal on your laptop (or on your VPS over SSH — start it inside tmux or screen so it survives you disconnecting):

claude remote-control

This prints a session URL and, if you press the spacebar, a QR code. Scan it with your phone's camera to open the session directly in the Claude app or your phone's browser. From there you can read Claude's output, answer permission prompts, and send new messages — all while the actual work happens back on your machine.

A few real constraints: it requires a Pro, Max, Team, or Enterprise plan (not a bare API key), your machine has to stay reachable (an outage of more than about 10 minutes ends the session), and a handful of terminal-only commands (like /plugin) simply don't work from the phone side — everything else does.

I5. Claude Code on the web — real cloud sessions, no laptop required at all

This is a genuinely separate, cloud-hosted version of Claude Code — not just a remote window into your machine. Go to claude.ai/code in any browser (including your phone's), sign in, and connect a GitHub repository once. From then on, describe a task, and Claude clones your repo into an isolated cloud machine, does the work, and pushes a branch for you to review — all without your laptop being involved at all.

This is the option that gets closest to "full Claude Code in a phone browser" for tasks that don't need your local setup:

"Fix the failing test in tests/test_auth.py and open a PR."

Sessions keep running even if you close the tab — start one on your laptop, walk away, and review the finished pull request from your phone later. You can also run several tasks in parallel, each in its own isolated session.

The trade-off: it only sees what's committed to GitHub (not uncommitted local changes), doesn't have your local MCP servers or tools, and offers a smaller set of permission modes (Accept edits, Plan, or Auto — no Manual or Bypass). For a well-defined task on a repo you already push to, none of that matters; for exploratory work that needs a lot of back-and-forth steering, Remote Control or your local terminal are still the better fit.

I6. Which one should you actually reach for?

• At your laptop, want to keep working normally? Just use the terminal, as this whole guide does.
• Started something at your laptop, want to check on it from your phone later? claude remote-control.
• Want to kick off a task from your phone with no laptop involved at all? claude.ai/code in your phone's browser, or the Code tab of the mobile app.
• Want Claude to handle something on your Desktop app while you're out, and get notified when it's done? Dispatch, in the Desktop app's Cowork tab — message it a task, and if it looks like development work, it spawns a Code session for you automatically.