Cloud sessions in Claude Code now set up your repo

Claude Code cloud sessions now prepare a repo’s environment on their own, Anthropic’s ClaudeDevs account said in a November 6 post on X. On Pro, Max and Ultra, Claude works out which dependencies, network access and API keys a project needs and saves that environment for next time, and the keys go into secure storage that Claude itself never sees.

Saving the environment matters because of how cloud sessions run. Each task gets a fresh virtual machine, so the saved environment is what keeps the next task from repeating the setup. The machine isn’t billed separately either: cloud sessions use the same usage limits as the rest of Claude Code.

Network access is one of the things Claude now decides for itself. Each task runs in a sandbox with network and filesystem restrictions, and Anthropic’s guide to cloud sessions describes users choosing which domains Claude Code can reach from it, for example allowing npm package downloads so Claude can run tests. Cloud environments also cover environment variables, setup scripts and environment caching, and the automatic setup now fills in that same environment.

Cloud sessions left research preview in September, and the same guide lists them as generally available on Team and on some Enterprise seats too. The automatic setup, though, is announced only for Pro, Max and Ultra, and Testing Catalog names the same three plans.