7 November 2026 · 3 min read
Claude Code Cloud Now Automatically Sets Up Repo Dependencies and API Keys
Anthropic announced on 6 November 2026 that Claude Code cloud sessions on Pro, Max and Ultra plans can automatically detect dependencies, network access and API keys, saving the environment for future sessions.
On 6 November 2026, Anthropic announced that Claude Code cloud sessions can now automatically configure a repository’s environment. The @ClaudeDevs account posted that Claude figures out what dependencies, network access, and API keys a project needs, then saves that environment for next time [1][2]. The feature is available on Pro, Max, and Ultra plans.
What changed
Previously, starting a cloud session with a new repository often meant hitting missing libraries, blocked network calls, or absent API keys. The Default environment carried no configuration of its own: no environment variables, no setup script, and network access limited to Trusted (package registries and approved domains) [1]. Users had to manually create an environment, specify a Bash setup script, and add keys. That loop of discovering what was missing, fixing it, and retrying is now cut out.
Now, on the first launch, Claude works out the three things a project needs:
- Dependencies – which libraries or tools to install.
- Network access – which hosts the session must reach.
- API keys – which external service credentials are required.
It then saves the resulting environment so that subsequent sessions on the same repository do not repeat the work [1][2].
How API keys are handled
The announcement states that API keys are saved securely and Claude never sees them [1][2]. This matches the existing network secrets mechanism described in Anthropic’s documentation. With network secrets, the agent proxy adds the key to requests after they leave the session’s virtual machine, so the key itself never enters the VM [1][2]. This matters because a key that never touches the VM cannot be exfiltrated by a compromised agent or sandbox escape. (A previous SOCKS5 flaw in Claude Code’s network sandbox, documented by researcher Aonan Guan, allowed credentials to be smuggled out between October 2025 and April 2026 [1].)
However, the announcement does not explicitly name network secrets, nor does it explain how a user supplies the value of a key that Claude has flagged as necessary [1].
Availability
The feature is announced for Pro, Max, and Ultra plans [1][2]. Ultra is the new name for the former Max 20x plan ($200/month), while Max is the $100 plan [1]. Cloud sessions can be started from claude.ai/code, the desktop app, the mobile app, or the terminal with claude --cloud [1].
Team and Enterprise plans are not mentioned in the post. The documentation states that on those plans a form appears for manual environment configuration unless an Owner has enabled quick setup [1]. Whether automatic setup will reach those plans is not established [2].
What is not yet clear
- The documentation page on cloud environments, as of 7 November, still describes only manual configuration and does not mention automatic detection [1]. It is unknown which files Claude reads or what rules it follows to decide on dependencies and network hosts.
- The post does not say whether the user must approve the network hosts Claude opens or the keys it requests. Before using the feature with production credentials, it is worth opening the saved environment and checking its contents [1].
- The mechanism for providing key values is not described [1].
What it means for developers
For developers using Claude Code cloud sessions, the change reduces the friction of moving a project from a local machine to the cloud. A repository that runs locally but stalls on a clean cloud VM can now be made ready without manual trial and error. The automatic saving of the environment means that once a project is set up, team members (on the same plan) can start working faster.
The secure handling of API keys, if it indeed uses network secrets, is a meaningful step. It keeps credentials outside the agent’s reach, lowering the risk of accidental exposure or deliberate exfiltration.
Still, the feature is new and its boundaries are not fully documented. Developers should treat the automatically created environment as a starting point and verify that network access and keys match their security requirements, especially for projects that touch production services.
Sources
- Claude Code cloud launches automatic dependency and API key setup
- Claude Code Cloud Now Sets Up Repos and API Keys on Its Own - FourWeekMBA
- claude code
- cloud
- environment setup
- anthropic
- api keys
Researched and drafted with AI from the sources above.
Learn to build with AI
Hands-on tutorials on Cursor, Claude Code, AI agents and more.