Cloud Threads
Run each Thread in its own managed environment.
Each Cloud Thread owns an isolated sandbox. Its Workspace can also contain Local Threads and other Cloud Threads using different repositories.
Lifecycle
Opening a Thread displays its saved conversation without waking the sandbox. Sending a message starts or wakes the environment, with progress shown in the conversation.
Review, files, terminals, and running previews require the runtime. When it is asleep, these panels offer a Wake action. The Checks tab shows relevant pull requests, checks, and file diffs. The workspace menu contains the general pull request browser.
The Thread tab opens immediately and preserves its layout while these steps run. Worktree stops billing when the sandbox is stopped. The selected idle timeout stops an inactive sandbox automatically.
Start a Cloud Thread
Choose a Workspace, select Cloud, and select the repositories the Thread may use. Repository access follows the connected GitHub accounts and Workspace repository permissions.
The first message creates the environment even if it is only a greeting. Repositories are cloned when the agent needs them. The agent can use ordinary Git for authorized private repositories without displaying a separate GitHub clone tool.
Start and stop the sandbox from the Thread's More options menu.
Preview
Start a web development server in the Cloud Thread, then open Preview from the side panel. The Preview picker lists application names and their running ports.
Each preview uses a separate preview-<id>.tryworktree.com origin. The desktop grants access only to an authenticated member of that Workspace; possessing the URL alone does not grant access. Preview authentication is kept separate from the application server and Worktree's main browser session.
Preview is currently available for Cloud Threads. Local previews and remote desktop access are not included.
Runtime sizes
| Size | Resources | Rate |
|---|---|---|
| Small | 1 vCPU, 1 GiB RAM | $0.30 / runtime hour |
| Standard | 2 vCPU, 4 GiB RAM | $0.60 / runtime hour |
| Large | 4 vCPU, 8 GiB RAM | $1.20 / runtime hour |
| Premium | 8 vCPU, 16 GiB RAM | $2.40 / runtime hour |
Plus supports Small and Standard. Pro and Team Core add Large. Team Scale supports every size, including Premium.
Idle timeout choices
- Plus: 15 minutes.
- Pro and Team Core: 15, 30, or 60 minutes.
- Team Scale: 15, 30, 60, or 120 minutes.
Billing model
Cloud is billed for awake sandbox runtime, not per viewer. Five people viewing one running Thread do not create five runtime charges. Three running Cloud Threads consume three sandboxes' runtime credits, even when they belong to the same Workspace.
When prepaid credit reaches zero, Worktree blocks new starts and safely stops billable runtimes rather than creating debt.
