Cloud

Run Proliferate workspaces away from your laptop.

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 should run without tying up your local checkout.

Cloud workspaces

A cloud workspace is a remote repository environment with a Proliferate runtime running inside it.

In a cloud workspace, Proliferate can run:

  • Agent chats and sessions.
  • Terminal commands.
  • Tests and setup scripts.
  • Browser or preview workflows when configured.
  • Git review for the workspace diff.

For normal coding work, Proliferate can reuse a repo environment and create multiple workspaces inside it. This keeps dependencies warm and makes cloud work feel fast.

Configure cloud

Configure cloud from the repository or workspace settings.

Common settings include:

  • Setup script.
  • Run or preview command.
  • Default branch or workspace target.
  • Agent credentials available in the cloud environment.
  • Idle timeout.
  • Cloud usage limit.

Use setup scripts for dependency installation and repository bootstrapping. Use run commands for the app, server, or preview process you want available while the agent works.

Move between local and cloud

Local, worktree, and cloud workspaces all revolve around the same repository work: branches, diffs, files, chats, and review.

Start locally when you need your machine, local tools, or an existing checkout. Start in cloud when you want the work to continue remotely.

To move work between local and cloud:

  • Push or publish the branch from one workspace.
  • Open or create a workspace for the same repository in the other target.
  • Continue from the branch or review the diff in Proliferate.

The handoff should stay git-backed. Cloud is not a replacement for reviewing the branch; it is another place where the workspace can run.

Usage and lifecycle

Managed cloud usage consumes Proliferate cloud credits or overage.

Cloud workspaces should stop when they are no longer active. Use idle timeout, manual stop, and usage caps to keep cloud work predictable.

Info:

Cloud workspaces use real compute. Long-running environments should have an idle timeout or a usage cap.

Isolation

Worktrees isolate workflow and branch state. Cloud environments isolate execution away from your laptop.

Computer-use or untrusted browser work should use stricter isolation when that capability is enabled.

Plugins

Extend Cowork and coding agents with tools, connectors, and custom capabilities.

Organizations

Teams, seats, and shared settings.

On this page