Code Cloud runs coding tasks in a managed cloud sandbox instead of on your computer. You prepare a reusable environment once, and tasks start from it. Cloud runs are saved on the server, so they carry on if you close the app or your laptop sleeps.
Start with your project
Open Settings > Coding > Code Cloud. On the Environments tab, choose Create environment. The Create a cloud environment dialog lists your GitHub repositories; connect GitHub if you have not, select one or more, and choose Get started. Use Configure access if a repository is missing.
ZeroTwo then opens a Cloud environment setup chat. It decides what needs installing and how the project should be configured, and asks you to review changes and supply details as it goes. Environments are private to you.
Configure the environment
An environment holds an install script, a start skill, environment variables, secrets and an internet-access policy. The setup chat fills most of this in for you; edit any part from the environment's page in Settings.
- Environment variables: up to 100 per environment. Names cannot start with
LD_,GIT_,E2B_orZEROTWO_. - Secrets: up to 50. Each secret lists the domains it may be sent to. Values are write-only, so they are never shown again.
- Vault: the Vault tab keeps variables and network secrets apart from any one environment, and an environment can take them "From your vault".
- Internet access: see Code Cloud internet access.
Review and publish
Your changes are a draft until you publish them. Use the Publish button, which reads Save & publish when you have unsaved edits. When it shows Environment published · Start a task, the environment is ready. Publishing takes a snapshot of the prepared machine, and republishing replaces it. Only a published environment can start a task.
Start a task
In the composer, choose Cloud as the location. In Work the location pill reads Work locally or Cloud. In Code it offers Local, New local worktree and Cloud, and the Choose environment pill selects the environment to start from. The project needs a Git remote. Describe the job and send it.
Keep work moving
A cloud task keeps running in its sandbox without your computer. On the desktop app, /cloud ("Run this chat in the cloud") moves a chat to the cloud, and on Ultra plans Settings > General > Keep working in the cloud moves a local Code task to the cloud when your computer goes offline, and applies the result when you return.
Review the work
Open the review pane to inspect what changed, using the Last turn scope, then ask for follow-ups in the same chat. Cloud tasks run with full access inside their sandbox, with no permission picker, so the environment's internet policy is what limits them.