Overview
Workspaces connect agents to repositories, branch state, tools, terminals, browsers, and review.
A workspace is the unit of agent work in Proliferate.
Use a workspace when the result should be tied to a repository, branch, diff, test run, pull request, or review. Each workspace gives agents the context they need without mixing unrelated work into one session.
What a workspace contains
A workspace can include:
- A connected repository.
- One execution target: your local checkout, a fresh worktree, or a cloud sandbox.
- A setup script and a run command for that repository.
- Agent sessions and chats.
- Terminals and a browser preview.
- Files, git diffs, and pull request status.
Choose the right workspace type
You pick where a workspace runs when you create it, from the same picker used to start a new chat.
| Type | Use it when |
|---|---|
| Work locally | You want the agent to work directly in an existing checkout. |
| New worktree | You want a clean branch and working tree for one reviewable task. |
| Cloud | You want agent work to keep running away from your laptop. |
Workspace target picker
The 'value ▾' control in the composer footer, open to show Work locally, New worktree, and Cloud options for the selected repository.
For most implementation work, a new worktree is the safest starting point because it keeps agent edits away from your primary checkout.
The target you pick stays fixed for that workspace. If you want the same task to continue somewhere else, publish the branch and open a new workspace against it there. See connect a repo for how repositories, checkouts, and cloud sandboxes relate.
Next: connect a repo.