Use this page when a cloud workspace won't start, won't connect, or stops returning results partway through a run.

A cloud workspace runs your repository on remote compute that Proliferate manages for you. Before any of that can happen, the repository has to be GitHub-backed and set up in Proliferate Cloud.

Check:

The repository is GitHub-backed and materialized in Cloud. Cloud environments only work for repositories hosted on GitHub. If it's the first time you're running this repo in the cloud, Proliferate needs to set it up there before a workspace can start.

Settings > Repo > Environment, cloud setup gate

The repo-scoped cloud settings empty state: a cloud icon, 'Not set up in Proliferate Cloud' heading, and a Set up Cloud environment button. Related states in the same slot: GitHub App not installed, Repository not covered, No access to this repository, and Reconnect GitHub App.

The GitHub App has access to this repo. Cloud environments read your repository through the Proliferate GitHub App. If an org admin installed the app but didn't grant it this specific repository, or your own GitHub App authorization expired, cloud setup blocks with a clear reason (installation missing, repo not covered, or your GitHub account lacks access).
The setup script succeeds. The setup script runs once when the cloud workspace is created, before any agent session starts. If it fails or hangs, nothing downstream will work. Check the script output in the workspace's terminal history.
The environment hasn't paused itself. Cloud sandboxes pause automatically after a period of inactivity to save compute. A paused workspace needs to wake up before it can run commands again, and waking up is subject to the same billing checks as starting a new one (see below).
You have cloud credits or overage available. Starting or waking a cloud workspace is blocked when your included usage is exhausted, your overage cap is reached, top-up is disabled, or a payment failed. Each of these shows a specific reason rather than a generic error.

Cloud workspace start-blocked banner

An inline banner shown when a cloud workspace can't start, with a title (for example 'Included usage is exhausted', 'Overage cap reached', or 'Payment needs attention') and a one-line explanation plus a fix action.

Agent credentials are available in the cloud sandbox. Cloud workspaces only have what you synced or what the gateway provides; native logins on your laptop don't automatically carry over. See agent credential issues if an agent that works locally fails only in the cloud.

Cloud and local aren't the same workspace you can flip between mid-task. You choose local, a new worktree, or cloud when you create the workspace. To move work to the other side, push the branch and open a new workspace against it there.

If the issue turns out to be usage or payment related, see billing issues for the full picture of plans, credits, and overage.

Cloud workspace issues