Claude Code Cloud Sessions Now Set Up Your Repository by Themselves
Claude CodeAnthropic announced that Claude Code cloud sessions on Pro, Max and Ultra can now work out what a repository needs to run, then save that environment for later sessions. Claude determines the dependencies, network access and API keys required. Anthropic says API keys are saved securely so Claude never sees them.
Key Takeaways
- Claude now infers a repository's needs for cloud sessions: dependencies, network access and API keys.
- The setup is saved for next time, so later sessions on the same repository skip the work.
- API keys stay hidden from the model, saved so that Claude never sees them.
- The announcement covers Pro, Max and Ultra, and does not say whether Team or Enterprise get it.
- Manual environment settings still work, including setup scripts and custom network allowlists.
- Details such as per-setting approval are unpublished, so teams with strict network rules should check what Claude saved.
Sources & Mentions
2 external resources covering this update
Less manual setup for cloud sessions
Anthropic announced on November 6, 2026 that Claude Code cloud sessions on the Pro, Max and Ultra plans are easier to get running against a real repository. Before this change, a developer had to configure a cloud environment by hand, using setup scripts, environment variables and network settings. Now Claude works out what the repository needs and saves the result.
What Claude figures out
According to the announcement, Claude determines three things for a repository: which dependencies to install, which network access the project requires, and which API keys it needs. It then saves the environment so that the next session on the same repository does not repeat the work.
How API keys are handled
The announcement says that "API keys are saved securely, so Claude never sees them." Anthropic's documentation describes a related mechanism called network secrets. A key is stored outside the session's virtual machine, and an agent proxy adds it to matching requests after they leave the VM. The documentation covers manually configured network secrets, so the exact way the automatic flow stores a key is not spelled out publicly.
What is not yet clear
The announcement names Pro, Max and Ultra and does not mention Team or Enterprise, so availability there is unconfirmed. It also does not say how Claude picks a network access level, or whether a user approves each saved setting. Manual environment configuration, with setup scripts, environment variables and the Trusted, None, Full and Custom network levels, remains available when the default allowlist is not enough.