Claude Code remote: ways to run it on a server

“Claude Code remote” can mean steering a session on your own computer from your phone, running sessions on machines somewhere else, or handing Claude work from a team chat. Claude Code’s own documentation lists several ways to work away from your terminal; they differ in what triggers the work, where Claude runs and how much you need to set up. [1] Here are five of Anthropic’s and one more: a team server, which is what we build.

Way 1 — Remote Control

Remote Control connects claude.ai/code or the Claude mobile app to a Claude Code session running on your machine. Claude keeps running locally, so your files, MCP servers, tools and project settings stay available, and the browser or phone is a window into that session. [1] Anthropic’s self-hosting page points here for one case in particular: to run Claude Code on your own always-on machine and drive it from other devices, use Remote Control. [3]

• What it needs. A Pro, Max, Ultra, Team or Enterprise subscription, signed in through claude.ai; API keys are not supported, and on Team and Enterprise an owner must turn it on first. It doesn’t work through Amazon Bedrock, Google Cloud’s Agent Platform, Microsoft Foundry, an LLM gateway or proxy, or a Claude apps gateway. Long-lived tokens from claude setup-token can’t start it. [1]
• The machine stays on. If the claude process stops, the session goes offline. [1] With claude remote-control, one process can hold several sessions (32 by default); by default they share the working directory, so they can conflict if they edit the same files. [1]
• Whose session it is. A session appears only in the claude.ai account that started it and grants no one else access. [1]

Fits when you are in the middle of work on your own computer, or keep Claude Code on an always-on machine, and want to drive it from your phone or another browser. [1][3]

Way 2 — cloud sessions (Claude Code on the web)

A cloud session runs on cloud infrastructure instead of your machine — Anthropic-managed by default. You start one from claude.ai/code, the Code tab of the Claude app, the desktop app or claude --cloud in the terminal, and connect GitHub so it can clone your code and push branches. [2] Cloud sessions are available on Pro, Max, Ultra and Team, and for Enterprise users with premium seats or Chat + Claude Code seats. A session can be shared by link, with sharing settings that differ for Team and Enterprise accounts. [2] Repository cloning in Anthropic-hosted environments and pull request creation require GitHub. [2] Cloud sessions continue with your laptop closed. [9]

Fits when you want to start a task with no local setup, work on a repo you don’t have cloned, or run several tasks in parallel. [1]

Way 3 — SSH from the desktop app

In the Claude desktop app, an SSH session runs Claude Code on a remote machine — your own server, a cloud VM or a dev container — while the app is the interface. [4] Several people can use the same machine: the desktop app installs its helper and Claude Code in the home directory of each user who connects. [4] With a Claude account, don’t count on a task to run overnight: its sign-in can expire after the desktop app disconnects. [4] The desktop app needs a paid subscription. [5]

Fits when the code lives on a server or VM with the hardware or dependencies it needs, and the people working on it use the desktop app. [4]

Way 4 — self-hosted environments

A self-hosted environment executes cloud sessions on infrastructure your organization operates. Repository checkouts, build artifacts, secrets and files the session creates stay on your machines; the conversation itself, including prompts, responses and tool results, still goes to Anthropic, and the control plane stays Anthropic-hosted. [3] Self-hosted environments are in public beta on Team and Enterprise plans and are off by default, and Anthropic notes that most teams are better served by Anthropic-hosted environments. [3]

Fits when a development team already uses cloud sessions and its checkouts, build artifacts and internal services must stay inside the company network. [3]

Way 5 — Claude in Slack

With Claude Tag, anyone in a Slack channel can tag Claude into a problem and hand it work, such as reproducing a bug and opening a pull request or turning a decision thread into a doc. [8] Slack users don’t each need a Claude seat to work with Claude in channels; that work is billed by usage from a balance an owner funds. [8] Claude works in an ephemeral sandbox, not on anyone’s computer. [8] It is available on Team and Enterprise plans, in public beta. [8]

Fits when a team already works in Slack and wants to hand Claude tasks where the conversation is.

Also from Anthropic. Dispatch lets you message a task from the Claude app to the desktop app on your computer (Pro, Max or Ultra). [9] Channels push messages from Telegram, Discord or iMessage into a session on your machine, and work with a claude.ai sign-in or a Console API key (research preview). [10] Scheduled tasks can run in the CLI, the desktop app or the cloud. [1]

Way 6 — a team server for people who don’t use a terminal

This is what we built Trina AX to do, so here is how it works there. Claude Code (and Codex) run on one company server, and everyone else uses a chat app in the browser, on desktop or phone. [6]

• Company files, checked per person. Folders are shared/, groups/, projects/ and personal folders, and the server checks every file the AI opens as the person asking. [6] The engine has no shell or file tools of its own and reaches files only through the server’s tools. [7] Removing someone’s folder access doesn’t erase earlier answers. [6]
• Connections. Claude Code with the company’s Claude account or each person’s own, or an API key with a monthly limit per person; use only accounts and plans authorized for your use. A person’s own connection is used first, and on new hosted teams one company connection can serve the whole team by default; the site notes that this setting doesn’t grant permission under Anthropic’s or OpenAI’s terms, that sharing one person’s subscription across a team can break them, and that a company API key with a monthly limit per person avoids that question. [6]
• Where it runs. A Linux server or an office Mac (no Codex on an office Mac) that the company runs, or a private Trina AX server for the company, in Seoul, that Trina hosts. [6]

What it doesn’t do. It is a pre-release with no security certification; development mode has no OS isolation, and a production install adds a dedicated account, a sandbox and a firewall. [7] Server operators, including Trina on a hosted plan, can read stored files and chats. [6] What the AI reads goes to the AI provider you connect; web searches, connected services, speech from files if allowed, and a periodic address check also leave the server. [6] The software is free to install yourself under AGPL-3.0; Trina hosting has a free plan for up to 3 people and paid plans from $50 a month, before tax, with AI usage paid separately to your AI provider. [6]

Fits when people who don’t use a terminal need Claude Code’s agent on shared company files, with each person’s folder access checked.

Side by side

	Where Claude runs	Who uses it	What it needs
Remote Control	Your machine, which has to stay on [1]	You, in your claude.ai account [1]	A Claude subscription; no API keys [1]
Cloud sessions	Anthropic-managed cloud, or your self-hosted environment [2]	You; sessions can be shared by link [2]	Pro, Max, Ultra or Team, or certain Enterprise seats; GitHub [2]
SSH (desktop app)	A remote machine you connect to [4]	Each person from their own desktop app; several can use one machine [4]	A paid subscription for the desktop app [5]
Self-hosted environments	Your organization’s infrastructure; the conversation goes to Anthropic [3]	Your organization’s developers [3]	Team or Enterprise, public beta, off by default [3]
Claude in Slack	An ephemeral sandbox [8]	Anyone in the channel; no seat needed for channel work [8]	Team or Enterprise, public beta; usage billed from a balance [8]
Team server (Trina AX)	One company server [6]	Everyone, in a browser chat app [6]	A Claude account or API key, and a server you run or Trina hosts [6]

How to choose

1. You want to keep working on your own computer from your phone → Remote Control, or Dispatch on Pro, Max and Ultra.
2. You want tasks to run with your computer off → cloud sessions; with self-hosted environments if checkouts must stay inside your network.
3. The code lives on a server and you work in the desktop app → SSH.
4. The team already works in Slack → Claude in Slack.
5. People who don’t use a terminal need the agent on company files, each with their own folder access → a team server.

Questions people ask

Can I run Claude Code on a server and use it from my phone?

Yes. Anthropic’s answer for your own always-on machine is Remote Control: start it there and connect from claude.ai/code or the Claude app. [1][3] If the machine will be off, use cloud sessions. [9]

Does Remote Control work with an API key?

No. It needs a claude.ai subscription sign-in, and long-lived claude setup-token tokens can’t start it either. [1] Channels, a different way to reach a session from your phone, also work with a Console API key. [10]

What’s the difference between Remote Control and Claude Code on the web?

Remote Control runs on your machine with your local tools; a cloud session runs on cloud infrastructure, Anthropic-managed by default. Both use the claude.ai/code interface. [1]

Can a whole team share one Claude Code server?

A Remote Control session belongs to the account that started it. [1] Several people can open SSH sessions on the same machine, each from their own desktop app. [4] Developers can run the organization’s cloud sessions in a self-hosted environment [3], anyone in a Slack channel can hand Claude work through Claude Tag [8], and a team server like Trina AX gives everyone one chat app on a company server with each person’s folder access checked. [6]

Try it

• Remote Control: run claude remote-control in your project directory. [1]
• Cloud sessions: start one at claude.ai/code. [2]
• Trina AX: Prepare for Trina hosting and Add Trina AX to your phone. Source: github.com/trina-app/trina-ax. Hosting plans: ax.trina.app/#pricing.

Claude is a trademark of Anthropic. Trina AX is made by Trina Inc. and is not affiliated with Anthropic.