Claude Code desktop and web
Claude Code is not terminal-only. Desktop and web surfaces add visual diff review, parallel sessions, cloud handoff, and mobile continuation when a GUI fits the task better than a shell.
- Last verified
- Applies to
- Claude Code 2.1.x. CLI spellings were checked on local version 2.1.198; official docs may describe newer 2.1.x behavior.
- Verification method
- Desktop Code-tab, local/SSH sessions, worktrees, connectors, provider differences, and handoff behavior were reviewed in official docs. The desktop app and external accounts were not operated.
- Official sources
- Desktop applicationSessionsChangelog
Reproducible practice
Run one disposable desktop session with a reviewable filesystem boundary
Prove repository selection, change isolation, evidence review, and cleanup before using parallel or remote desktop workflows.
Prerequisites
- Claude Desktop on a supported OS and an authorized account.
- A trusted repository with a clean baseline and no production secrets.
- A disposable branch or worktree and one targeted verification command.
Steps
Create the isolation boundary
Use normal git tooling before opening Desktop so the baseline remains independently verifiable.
Step 1 git status --short git switch -c desktop-labOpen the exact repository
Confirm displayed path, provider, permission mode, and session type before sending a task.
Request one bounded change
Require the same test command and diff evidence used outside Desktop; GUI behavior was not tested in this audit.
Review outside the app
Inspect status, diff, and tests in a trusted terminal before keeping or sharing the session.
Step 4 git status --short git diff --check git diff --stat
Expected result
The session affects only the disposable branch or worktree, produces a reviewable diff, and passes the named external verification command.
Validation
- Compare repository path and branch inside and outside Desktop.
- Inspect every changed file with git.
- Confirm session sharing, connectors, and remote access remain off unless explicitly required.
Failure handling
Wrong repository opens
Stop before granting tools and reselect the exact path.
Provider differs from CLI
Check Desktop provider configuration separately; do not assume CLI environment variables apply.
Cleanup or rollback
- Close the session, inspect the diff, then delete only the disposable branch or worktree through normal git review.
- Revoke connectors or remote access enabled solely for the exercise.
Boundaries and when not to use it
- Desktop and CLI differ in providers, connectors, plugins, and authentication behavior; validate the active surface.
- Parallel sessions can still conflict when they share files or external systems; use worktrees and scoped credentials.
Desktop app
The desktop app supports parallel sessions, git-isolated worktrees, integrated terminal and file editing, visual diff review, and handoff from terminal sessions.
| Command | Description |
|---|---|
/desktop | Continue the current session in Claude Code Desktop. |
/app | Alias for /desktop on supported platforms. |
Parallel sessions
Run multiple tasks with isolated worktrees instead of juggling one terminal thread.
Read guideVisual review
Inspect proposed edits in a GUI when side-by-side diff review is faster than terminal output.
Read guideTerminal handoff
Use /desktop or /app to continue a CLI session in the desktop app.
Read guideWeb and cloud sessions
Claude Code on the web runs in Anthropic-managed environments. It is useful for tasks that benefit from cloud isolation, PR workflows, or working without local setup.
| Command | Description |
|---|---|
claude --cloud | Create a new web session with a task description. |
/teleport | Pull a web session into the current terminal. |
/remote-control | Continue a local session from another device or browser. |
Cloud tasks
Good for long-running reviews, repo exploration, and PR-oriented work when local setup is limited.
Read guideTeleport
Move between web and terminal without losing the thread of work.
Read guideRemote Control
Keep coding on desktop while monitoring or steering from phone or browser.
Read guideChoose the right surface
Terminal remains best for scriptable automation and deep shell workflows. Desktop and web are stronger for visual review, parallel work, and mobility.
Use terminal when
You need pipes, CI-style automation, SSH remote machines, or tight git shell integration.
Read guideUse IDE when
Selected-code edits, inline diffs, and editor navigation matter most.
Read guideUse desktop/web when
You want parallel sessions, GUI review, or continuation across devices.
Read guideSetup checks
Desktop and web features depend on account access, platform support, and sometimes an existing CLI install for handoff commands.
claude auth status --text
claude --versionSetup
Confirm CLI install and PATH before using /desktop or /teleport.
Read guideAuthentication
Handoff fails silently when credentials expire mid-session.
Read guideSessions
Named sessions resume cleanly after desktop or web handoff.
Read guideChrome testing
Use browser sessions when GUI review needs live page interaction.
Read guideDesktop and web checklist
Confirm account access
Some desktop and web features require a supported Claude subscription or org access.
Read guideKeep CLI installed
Handoff commands still depend on a working local Claude Code install.
Read guidePick one primary surface
Start a task on the surface that matches review style, then hand off instead of restarting.
Read guideUse Remote Control intentionally
Enable remote continuation only when you need cross-device access for an active session.
Read guide