Local & cloud

Cloud workspaces run Proliferate work on remote compute instead of your laptop.

Use cloud when an agent should keep working while your laptop is closed, when you want a clean remote environment, or when a task shouldn't tie up your local checkout.

Cloud workspaces

A cloud workspace runs inside your personal cloud sandbox: a remote machine with the same Proliferate runtime that powers local work, kept warm and ready for you specifically.

That sandbox is shared across every repo you enable for cloud, not created fresh per repo or per workspace. The first time you set up a repo for cloud, Proliferate provisions your sandbox if you don't already have one, then clones and configures the repo inside it. Every cloud workspace you open after that, for any repo, reuses the same warm machine, so dependencies stay installed and new cloud workspaces start fast.

In a cloud workspace, Proliferate can run:

• Agent chats and sessions.
• Terminal commands.
• Setup and run scripts.
• Browser or preview surfaces, when the repo has a runnable app.
• Git review for the workspace diff.

Set up a repo for cloud

Cloud environments are available for GitHub-backed repositories. The first time you configure a repo for Cloud, Proliferate checks that the Proliferate GitHub App can access it:

• If the app isn't authorized for your GitHub account, you'll see a Connect GitHub App prompt.
• If the app isn't installed on the repo at all, an organization admin needs to install it.
• Once access is confirmed, click Set up Cloud environment to materialize the repo into your sandbox.

You don't need a local clone to do this. A repo can be cloud-only: add it straight from GitHub without ever checking it out on your machine.

Configure cloud

Cloud settings live in the same Settings → Repo tabs as local settings, switched to the Cloud context:

• Configure: the default branch cloud workspaces for this repo branch from, either the GitHub default or one you pick.
• Actions: a setup script that runs once when a cloud workspace for the repo is created, and a run command launched by the workspace's Run action.
• Environment: variables and files synced into this repo's cloud workspaces. Workspace-level values here override your personal and organization secrets, which are also available in your sandbox.

Local and Cloud never share these settings. A setup script you write for Local does not carry over to Cloud, and vice versa, so a repo can run a native install step on your machine and a container-friendly one in the sandbox. See Configuration for the full walkthrough.

Local or cloud, chosen up front

You pick a workspace's target when you create it: local checkout, new worktree, or cloud. That choice sticks for the workspace's whole life. Proliferate doesn't move a running workspace between local and cloud mid-task.

Because everything is git-backed, that's rarely a limitation in practice. Push the branch from one workspace, then open a new workspace on that branch in the other target and continue there. The code and history carry over even though it's a new workspace record, not the same one relocating.

Cloud lifecycle

Your cloud sandbox pauses when it's been idle, and wakes automatically the next time you open a cloud workspace or send it a prompt. Waking can take a few seconds while the sandbox resumes and the runtime reconnects.

Archiving, pruning, and deleting cloud workspaces follow the same rules as local ones: your chat history is durable and separate from the checkout on disk. See Lifecycle & storage for exactly what each action does and does not remove.

Usage and billing

Managed cloud usage draws on your Proliferate credits and can be capped by you or your organization. See Billing and limits for what counts toward usage and how caps work.