Claude Code in the terminal vs the desktop app

4 November 2026 · Daniel Bilsborough · Reviewed 4 November 2026

The comparison below is dated November 2026 and comes from Anthropic's documentation on the day it was written, with links to each page. Both products change often, so check the CLI comparison in the desktop docs for the current state.

Feature comparison (as of November 2026)

Sources: Desktop feature comparison, CLI system requirements, Claude Code overview, Desktop quickstart, all read 4 November 2026.

What the two share

Anthropic describes the desktop app as "the same underlying engine with a graphical interface." The two read the same configuration: CLAUDE.md files, MCP servers in ~/.claude.json or .mcp.json, hooks, skills and settings.json. The same models are available in both.

They can also run at the same time on the same project. Each keeps its own session list. Running /desktop in the terminal moves the current session into the app, and /resume inside the app picks up a session started from the CLI on that computer. The /desktop handoff needs a claude.ai subscription and works on macOS and x64 Windows.

Who each one suits, in Anthropic's words

The desktop docs put it in one line: "use Desktop when you want to manage parallel sessions in one window, arrange panes side by side, or review changes visually. Use the CLI when you need scripting, automation, or prefer a terminal workflow."

The platforms page lists the CLI as best for "terminal workflows, scripting, remote servers" and the desktop app as best for "visual review, parallel sessions, managed setup." It also calls the CLI "the most complete surface for terminal-native work."

Running Claude Code on another machine

Both versions can work on code that lives on a server. They do it in different ways, and the difference matters once a task runs for hours.

Desktop app: SSH sessions

The desktop app can open an SSH session: Claude Code runs on the remote machine and the app on your computer is the interface. The app installs a helper and Claude Code under ~/.claude/remote/ on the remote machine, which needs an SSH server with SFTP turned on.

If the computer running the app sleeps, loses its network or quits, the task carries on until it finishes, needs you, or hits a limit. Anthropic's docs list those limits plainly. With a Claude account sign-in, the docs say not to count on a task running overnight, because the app renews that sign-in only while it is running and connected. Connectors and other tools that run through the app fail while it is disconnected, and if the app doesn't connect for 30 days, the helper stops and ends its Claude Code processes. For work that has to continue with the computer asleep or off, the docs point to a cloud session instead.

Terminal: Claude Code on the server, inside Tmux

The CLI can run directly on the server. SSH in, start Claude Code, and the process belongs to that machine. Put it inside Tmux and it outlives the SSH connection: close the laptop, lose signal on the train, and the session is still there to attach to later. Anthropic's Remote Control docs give the same advice: "If you run claude from a terminal on a remote machine, start it inside tmux or screen to keep the session running after you disconnect from SSH."

In this setup, the screen is whatever terminal attaches. A laptop, a desktop, an iPad and a phone can all attach to the same Tmux session, one after another, and see the same conversation.

Why the terminal version fits long-running agent work

• The always-on part is the server. A Mac mini at home or a VPS stays on. The device in your hand can come and go.
• Tmux holds the session. Detaching, a dropped connection or a locked phone only ends the view. tmux attach brings back the same screen, scrollback included.
• Any SSH client can be the screen. Nothing has to be installed on the device you steer from beyond a terminal.
• One session per agent. Several Claude Code sessions, or Claude Code next to Codex, each sit in their own named Tmux session on the same machine.
• Scripting and providers. Print mode, the Agent SDK, agent teams and third-party providers are CLI features, per the comparison above.

The desktop app has things the terminal doesn't: visual diffs, the app preview and simulator panes, file attachments, and Dispatch. If those are the main draw, the desktop app's SSH sessions bring some of that to a remote machine, within the limits listed above.

Set it up on a Mac mini or VPS

1. Make the machine reachable over SSH. On a Mac that's Remote Login in System Settings. A VPS usually has SSH on from the start. Away from home, a VPN such as Tailscale is one common way to reach a machine with no public address. The Mac mini agent setup covers a home machine in more detail.
2. Install Claude Code on that machine with Anthropic's install script, or with Homebrew on a Mac, then run claude once and sign in:

   curl -fsSL https://claude.ai/install.sh | bash
   # or, on a Mac
   brew install --cask claude-code

   Homebrew installs don't auto-update; brew upgrade claude-code updates them.
3. Start a named Tmux session and run Claude Code inside it, in the project folder:

   tmux new -s claude
   cd ~/projects/my-app
   claude

4. Add Anthropic's Tmux settings to ~/.tmux.conf, then run tmux source-file ~/.tmux.conf. Per the terminal configuration docs, these let notifications and progress updates through and let Shift+Enter insert a newline:

   set -g allow-passthrough on
   set -g focus-events on
   set -s extended-keys on
   set -as terminal-features 'xterm*:extkeys'

   set -g mouse on is worth adding too, for swipe and wheel scrolling through long output. The Tmux cheat sheet has the rest.
5. Detach and leave it working with Ctrl-b d. Later, from any device, tmux attach -t claude picks it up again.

Anthropic's own options for a phone

Anthropic offers three ways to reach Claude Code from a phone, all through the Claude app for iOS and Android. The docs describe that app as "a client for Claude Code sessions rather than a place where code runs."

• Remote Control connects the Claude app or claude.ai/code to a session running on your machine, from the CLI, the desktop app or VS Code. It needs a Pro, Max, Ultra, Team or Enterprise plan; API keys and third-party providers aren't supported. The machine has to stay on and the claude process has to keep running.
• Dispatch takes a task you message from the phone and can start a session in the desktop app. It needs a Pro, Max or Ultra plan and isn't available on Team or Enterprise.
• Cloud sessions run on Anthropic-managed infrastructure and keep going after you disconnect.

Remote Control and Tmux work together: a claude process inside Tmux on the server can also be the one the Claude app connects to. Claude Code on iPhone goes further into how these compare with a terminal on the phone.

Steer it from an iPhone or iPad with Shell Drop

Shell Drop is a free SSH terminal for iPhone, iPad and iPhone Duo, built for this loop. The phone attaches to the Tmux session on the server and shows the real Claude Code terminal, the same screen you'd see at a desk.

1. In Shell Drop, add a saved connection to the server, with a password or an SSH key. SSH keys on iPhone covers creating a key, including one in the Secure Enclave, and adding it to the server.
2. Connect, then attach: tmux attach -t claude.
3. Read what Claude did, type or dictate the next instruction, and press Return. Lock the phone when you're done; the session keeps running on the server.

What the app adds on top of a plain SSH session:

• Voice Drop. The mic on the keyboard toolbar transcribes on the phone with Apple speech, or with your own Groq key, and drops the words at the cursor. Nothing sends until you press Return.
• Screenshots and files. Paste a screenshot, or attach a file, photo or video from the toolbar. It uploads to the server over SSH and the path lands at the prompt for Claude Code to read.
• Agent needs you. A live activity on the lock screen and in the dynamic island, one row per Tmux session, turns orange when an agent stops at a prompt or waits on an approval. Off by default; turn it on in Settings > Agents > Live activities.
• Tmux on a touch screen. A vertical swipe scrolls history, a horizontal swipe changes sessions, and tab names can sync from Tmux, so each tab shows which agent it is.
• Clipboard back to the phone. With Settings > Agents > Let server send to clipboard on, Claude Code can put text on the phone's clipboard, ready to paste into another app.

The same server can run Codex in a second Tmux session; Codex on iPhone has that setup. Shell Drop has no account, no subscription and no telemetry.

Sources

All read 4 November 2026: Desktop application, Platforms and integrations, Overview, Advanced setup, Desktop quickstart, Remote Control, Claude Code on mobile, Configure your terminal.

Questions