Claude Code Cloud Sessions Are Generally Available: Remote Control and Web Sessions Explained

Cloud sessions are generally available

Anthropic’s updated cloud sessions announcement establishes the September 23 general availability date and the new name: cloud sessions, previously known as Claude Code on the web.

The original web product launched on October 20, 2025, as a beta research preview. The announcement still contains that original preview language below its dated update. For the product’s status on September 25, 2026, the September 23 update is the relevant statement.

Cloud sessions are available to:

• Pro users.
• Max users.
• Team users.
• Enterprise users with premium seats or Chat + Claude Code seats.

That list describes cloud-session eligibility. It does not establish a complete Remote Control eligibility matrix.

The cloud workflow lets you connect GitHub repositories, describe coding tasks, monitor progress, and steer execution from a browser. Each task runs in an isolated environment on Anthropic-managed infrastructure. Multiple tasks can run in parallel across repositories, with automatic pull-request creation and change summaries.

For broader navigation across Claude Code interfaces, see the web and desktop guide.

How claude code remote control differs from cloud sessions

The most useful distinction is where the code executes. A browser interface alone does not tell you whether Claude Code is working locally or in the cloud.

Remote Control is useful when the work needs to remain in your existing local environment while you steer it from another device. Cloud sessions are useful when you want a task to execute in an isolated environment managed by Anthropic.

Remote Control also predates cloud general availability. Claude Code v2.1.51, released February 24, 2026, introduced the claude remote-control subcommand. Its release notes described local environment serving “for all users,” but that wording is not enough to establish eligibility for every subscription tier.

Browser and mobile clients

The Remote Control documentation identifies claude.ai/code and the Claude iOS and Android apps as clients. That page is continuously updated, so it does not establish when each client became supported.

The original cloud announcement separately introduced access through the Claude iOS app. Keep those two pieces of evidence distinct: the dated cloud announcement establishes its original mobile access, while the live Remote Control page describes clients without a complete historical timeline.

Searching for “claude remote” or “claude code remote sessions” can therefore lead to two different workflows. Check the execution location before choosing commands or planning a handoff.

Start or reconnect to a local Remote Control session

The commands below are documented in the changelog available with the September 24 release. They cover starting local environment serving, exposing an existing conversation, naming a session, and resuming the most recent Remote Control session.

Start local environment serving

Run:

claude remote-control

This starts the Remote Control workflow for your local environment. Your computer remains the execution host; connecting from another device does not move the work into a cloud session.

To give the session a recognizable name:

claude remote-control --name "My Project"

Custom names were added in v2.1.69. A name helps identify the session you intend to connect to, especially when returning to work from another device.

Connect an existing conversation

Inside an existing Claude Code conversation, run:

/remote-control

You can also supply a custom session name:

/remote-control My Project

This enables remote access to the conversation already running locally. It is the relevant path when you have begun work in the terminal and want to continue steering that same local session from a browser or phone.

To resume the most recent Remote Control session from the command line:

claude remote-control --continue

The pre-cutoff changelog documents these commands. For related terminal commands, use the Claude Code CLI reference.

Enable Remote Control at startup

The pre-cutoff changelog confirms the configuration key remoteControlAtStartup and the interface label “Enable Remote Control for all sessions.”

The live documentation describes enabling it through /config, or setting the following in ~/.claude/settings.json:

{
  "remoteControlAtStartup": true
}

The dated evidence establishes the key and interface label. The live page supplies the file location and value, but it does not establish the complete historical rules for configuration scopes as of September 25. Avoid assuming additional scope or precedence behavior from this example.

Run cloud tasks and move them into your terminal

Cloud sessions begin with a connected GitHub repository and a task description. You can monitor progress and steer the task in the browser while execution happens in its isolated cloud environment.

Parallel tasks can span repositories, and the workflow supports automatic pull-request creation with change summaries. This makes cloud sessions a distinct execution option, even though you can interact with both cloud and local sessions through remote interfaces.

Understand the cloud environment

The announcement describes sandbox environments with network and filesystem restrictions. Repository access goes through a secure Git proxy, and network access is configurable—for example, to allow package downloads needed for tests.

Those settings matter when defining what a task must do. If the task needs packages to run its tests, the cloud environment needs the corresponding network access. The announcement does not establish a universal network configuration for every task.

Hand off cloud work to the terminal

Claude Code v2.1.0 added /teleport and /remote-env for claude.ai subscribers. The pre-cutoff changelog also documents this command for continuing a cloud session locally:

claude --teleport <session id>

The cloud-session documentation explains that teleport fetches the cloud branch and conversation history. Subsequent local work stays in the terminal’s copy.

That handoff changes where you continue working. If you then want to steer the local session from your phone, run:

/remote-control

The resulting sequence is straightforward: start the task in the cloud, bring its branch and conversation into your terminal, then enable Remote Control for the local continuation. After that handoff, keeping the computer and Claude process running is necessary for Remote Control.

Troubleshoot Remote Control and GitHub connections

Start with the execution location. A Remote Control connection depends on Claude Code running on your computer; a cloud session depends on its cloud environment and repository connection.

Check the local host and process

For Remote Control, verify that the host computer and Claude process are still running. The connection does not transfer execution elsewhere, so a stopped host or process cannot continue serving the local session.

If you intend to reconnect to your most recent Remote Control session, the documented command is:

claude remote-control --continue

For an existing terminal conversation, use /remote-control there. These commands address different starting points: resuming the most recent Remote Control session, or enabling access to the conversation you currently have open.

Check the documented debug fix

Claude Code v2.1.282, released September 24, 2026, fixed claude remote-control --debug failing with Unknown argument: --debug.

claude remote-control --debug

If that exact argument error appears, check the installed version against the release containing the fix. The brief establishes this specific bug and correction; it does not provide a complete troubleshooting matrix for other connection failures.

The same release added Claude GitHub App installation and connectivity status under Settings › Connectors › GitHub for cloud sessions. That status is relevant when investigating a cloud repository connection, while local host checks are relevant to Remote Control.

Cloud sessions share Claude Code usage limits

Cloud sessions share rate limits with other Claude Code usage. Moving a task into the cloud therefore does not create a separate usage allowance.

Starting September 14, 2026, Claude Code weekly limits became permanently 25% higher than their pre-promotion levels for Pro, Max, Team, and seat-based Enterprise plans.

This followed a temporary 50% increase that ran from May 13 through September 13, 2026. The weekly-limits announcement distinguishes the temporary increase from the permanent one. The promotion did not affect five-hour limits and excluded Free plans and consumption-based Enterprise seats.

You can inspect limits in the CLI with:

/usage

For a broader explanation of the usage model, see the Claude Code rate-limits guide. The established facts do not support a numerical session capacity or a fixed number of parallel tasks for each plan.

Key takeaways

• Cloud sessions became generally available on September 23, 2026, replacing the earlier Claude Code on the web name.
• Remote Control keeps execution and filesystem access on your computer; cloud sessions execute on Anthropic-managed infrastructure.
• Use claude remote-control to start local environment serving, or /remote-control to enable access to an existing conversation.
• Use claude --teleport <session id> to continue cloud work locally, then /remote-control if you want remote access to that local continuation.
• Cloud sessions share Claude Code usage limits; /usage displays limits in the CLI.

FAQ

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

Remote Control connects a browser or phone to Claude Code running on your computer, where execution and filesystem access remain local. Cloud sessions, previously called Claude Code on the web, execute in isolated environments on Anthropic-managed infrastructure.

How do I continue a terminal session from my phone, and must my computer stay awake?

Run /remote-control inside the existing Claude Code conversation to enable remote access. Your host computer and Claude process must keep running because execution remains local.

Which plans include cloud sessions, and do they share usage limits?

Cloud sessions are available to Pro, Max, Team, and Enterprise users with premium seats or Chat + Claude Code seats. They share rate limits with other Claude Code usage, and /usage displays limits in the CLI.

How do I move a cloud session into my terminal?

Run claude --teleport <session id> to continue the cloud session locally. Teleport fetches the cloud branch and conversation history; subsequent work stays in the terminal’s copy, where you can run /remote-control to enable remote access.