Four surfaces, two places where code runs
The question that matters is not which window you type in, but where the work happens: on your computer, or on a cloud machine. As of November 2026:
| Surface | Where Claude works | Needs | Strong at |
|---|---|---|---|
| Terminal CLI | Your machine | Paid plan, Console API key, or a cloud provider such as Amazon Bedrock | Everything: all commands, scripting with claude -p, CI |
| Desktop app, Code tab | Your machine, a cloud machine, a server over SSH, or WSL 2 | Paid Claude subscription | Visual diff review, parallel sessions, previews, PR follow-up |
| Web, claude.ai/code | Anthropic-managed cloud VM (or your org’s self-hosted environment) | Pro, Max, Ultra, Team, or Enterprise with premium or Chat + Claude Code seats | Long tasks that keep running with the laptop closed, many tasks in parallel |
| Mobile, Code tab in the Claude app | Nowhere itself: it steers cloud or local sessions | claude.ai account | Checking in, answering questions, steering |
The docs say each surface connects to the same engine, but cloud sessions load only a subset of your configuration: your user and local settings stay on your machine, and MCP servers do not automatically carry over. What you commit to the repo, such as CLAUDE.md and .claude/settings.json, comes along with the clone. IDE extensions for VS Code and JetBrains are a fifth route; see Claude Code in VS Code and JetBrains.
What each one is
- Terminal CLI. You run
claudein a project folder. It reads and edits files and runs commands on your machine. Together with the VS Code and JetBrains integrations, it is where third-party providers such as Amazon Bedrock work, and it is the one you script: pipe a log intoclaude -p, run it in CI. Install steps are in how to install Claude Code. - Desktop app. The Code tab in the Claude desktop app for macOS, Windows (x64 and ARM64) and Linux (beta, Ubuntu and Debian). Each conversation is a session with its own folder, and you can run several side by side; turn on Worktree to give a session its own copy of the repo. You review changes file by file and comment on lines, and with the GitHub CLI installed it can watch a pull request: Auto-fix handles failing CI and new review comments, Merge when ready turns on auto-merge. A session can be Local, Cloud, SSH or WSL.
- Claude Code on the web. At claude.ai/code you pick a GitHub repository and describe the task. An isolated VM clones the repo, works, and pushes a branch. The session keeps going after you close the tab. Network access is limited by default and set per cloud environment.
- Mobile. The Claude app for iOS and Android is a client, not a place where code runs. From its Code tab you start or follow cloud sessions, drive a session on your own computer through Remote Control, or message Dispatch a task for the desktop app (Dispatch is Pro, Max and Ultra only).
Moving work between them
Sessions are not stuck where they started:
claude --cloud "Fix the flaky test"starts a cloud session for the current repository from your terminal. The older--remotespelling still works.claude --teleport, or/teleportinside a session, pulls a cloud session into your terminal: it checks out the branch and loads the conversation./desktopcontinues the current terminal session in the desktop app (macOS and x64 Windows)./remote-controlmakes a local session reachable from your phone or browser.
From the CLI the handoff to the cloud is one-way: you can pull cloud sessions down, but not push an existing terminal session up. The desktop app can send a local session to the cloud from its Open in menu.
The misunderstanding: “claude.ai/code is my laptop in the browser”
Two different things share the claude.ai/code interface. A cloud session runs on Anthropic’s VM and clones your GitHub remote at your current branch, not your local checkout, so local commits you did not push are not there. A Remote Control session runs on your own machine, with your files, tools and MCP servers, and stops when your machine or the claude process stops. Pick cloud for work that should run without you; pick Remote Control for work that needs your local setup.
Which one to pick
- You live in the terminal or need automation: the CLI.
- You want to see diffs and run three tasks side by side without juggling terminals: the desktop app.
- The task is long, the repo is on GitHub, and you want to close the laptop: the web.
- You are away from your desk: mobile, steering whichever of the above is running.
Usage counts the same everywhere: cloud sessions share the rate limits of your account, so parallel tasks use your plan faster. See Claude Code usage limits.
What this means for a team
Settings that travel are the ones in the repository. A cloud session reads what is committed, and the docs note that a cloud session on Anthropic’s machines does not read a device’s MDM policy, only server-managed settings. Desktop connectors and plugins sync through the claude.ai account, not through the CLI’s ~/.claude folder. So the same developer can get slightly different context depending on the surface, and two developers on different surfaces even more so. The project CLAUDE.md is the common ground; see how Claude Code memory works.
Where Bombos fits
Switching surfaces is easy; keeping the same knowledge behind each one is not. Bombos is a plugin that gives Claude Code, on any surface, and the team’s other AI tools one shared memory: team knowledge, learned rules, and what already sits in mail, documents and repos, traceable to the source, in the cloud or on your own server. One developer can try it on their own agents first.
Related questions
Do I need the CLI to use the desktop app?
No. The desktop app includes Claude Code, so you do not install the CLI separately. You do need a paid Claude subscription.
Do cloud sessions cost extra?
No separate charge for the cloud machine. Cloud sessions count toward your plan's usage limits together with the rest of your Claude and Claude Code use.
Can I move a session from my terminal to the desktop app?
Yes. Run /desktop in the terminal to continue the session in the desktop app. It needs macOS or x64 Windows and a Claude subscription.
Does Claude Code on the web work with GitLab or Bitbucket?
Cloning and pull requests in Anthropic-hosted cloud sessions need GitHub. You can upload another repository as a local bundle with CCR_FORCE_BUNDLE=1, but the session cannot push back to that remote.
Is there a separate Claude Code mobile app?
No. Claude Code lives in the Code tab of the regular Claude app for iOS and Android.
