Claude Code in the cloud sets up repositories on its own

What's new

Anthropic has changed how you get started with Claude Code in the cloud, according to a blog post that reproduces a post from the @ClaudeDevs account on November 6, 2026. Previously, users had to set up an environment themselves. Now cloud sessions set up a repository on their own, meaning a project's complete code and files.

Claude assesses which dependencies (the software packages the project is built on), which network access and which API keys (credentials for other services) the project needs. Claude then saves the environment for the next session. Users therefore don't have to do it manually in their first cloud session. According to the announcement, it applies to Pro, Max and Ultra plans.

What's smart

The tedious groundwork goes away. Many people know the drill of installing packages, opening up the right web addresses and adding keys before anything works at all. Here Claude does it for you, and the next session starts with the saved environment.

Security has been considered as well. The announcement states that API keys are stored securely so that Claude never sees them. Anthropic's documentation generally describes keys added as network secrets as sitting outside the sandbox, the isolated area where Claude works. A proxy, a kind of intermediary, adds the keys to the right requests after they have left the session. It has not been confirmed, however, that the automatic setup uses that mechanism. GitHub credentials remain encrypted at Anthropic and never enter the session's virtual machine. A newly created default environment has the network access level "Trusted."

Sessions can be started from claude.ai/code, the mobile app, the desktop app and from the terminal with the command "claude --cloud."

Cheaper or better?

There is no separate charge for the cloud machine. Usage counts toward the plan's usage limits along with other Claude and Claude Code use, and running several sessions at once uses up correspondingly more of the limits. Monthly prices are not stated in the sources, and it is also unclear how the feature compares with competitors or whether it is separately available in Denmark and the EU.

Cloud sessions are generally available on Pro, Max, Ultra and Team, as well as for Enterprise users with premium seats or Chat + Claude Code seats. It is not clear whether the automatic setup also applies to Team and Enterprise, since the announcement mentions only Pro, Max and Ultra.

There are also limitations. Cloning repositories in Anthropic-hosted environments and creating pull requests (proposals for code changes) require GitHub. Code from GitLab, Bitbucket and similar services can be sent as a local bundle, but the session cannot push results back. Organizations with Zero Data Retention, HIPAA configuration or customer-managed encryption keys cannot use cloud sessions, and the sessions are not available through Amazon Bedrock, Google Cloud or other third-party providers. A setup script is cached only if it finishes in about five minutes.

What it's good for

The feature suits developers and small teams who keep their code on GitHub and want to get Claude going without first spending time on setup. It is especially handy if you want to start a task from your phone or browser and let it run in the cloud.

How well the automation works in complex projects such as monorepos (many projects in one repository) and private package registries is not documented. The sources also don't say which files Claude reads to find dependencies and keys, or whether the user has to approve what it finds before it is saved. Companies with strict data-handling requirements should check the list of exclusions above first.