On November 6, 2026, ClaudeDevs announced automatic setup for Claude Code cloud sessions on Pro, Max, and Ultra. The feature is intended to identify a repository’s dependencies, network access, and API keys, then save the environment for later sessions, according to ClaudeDevs’ announcement.
What the announcement says Claude will prepare
The announced setup covers three parts of a project’s environment: software dependencies, network access, and API keys. ClaudeDevs said the setup would be saved for the next session and that the keys would be stored securely so Claude would not see them. The post names Pro, Max, and Ultra.
Anthropic’s existing cloud-environment tools explain two ways to configure a session, but describe different steps in its lifecycle.
Setup scripts run before launch; hooks run after
A setup script provisions the cloud virtual machine before Claude Code starts. It can install tools and dependencies. A SessionStart hook runs after Claude Code launches and can run in cloud sessions as well as local ones, according to Anthropic’s cloud-environment documentation.
Setup scripts prepare the cloud machine before launch; SessionStart hooks run after Claude Code starts.
The timing changes what each tool handles: scripts prepare the machine itself, while a hook can perform work when a session starts or resumes. The documentation also describes network access settings named None, Trusted, Full, and Custom, with Trusted as the default.
What the setup cache keeps
Anthropic says a setup script that finishes in roughly five minutes can be cached as a filesystem snapshot. That snapshot preserves installed packages and files, not running processes. A later session can therefore reuse the prepared files without carrying over a process that was running when the snapshot was made.
How the announcement describes API keys
ClaudeDevs said the announced setup would save API keys securely and keep them out of Claude’s view. Anthropic separately documents an API-credential proxy for cloud environments: it attaches a stored credential to requests for specified hosts after requests leave the virtual machine, keeping the key out of Claude, commands, and session environment variables. The documentation describes that proxy as a credential mechanism; the announcement does not identify it as the implementation behind automatic setup.
