Workspaces
A workspace is one repository, one branch, and one active execution target, with sessions, terminals, browsers, and review attached to it.
A workspace is one repository, one branch, and one active execution target — not one runtime. A single runtime serves many workspaces at once: on your machine one shared AnyHarness runtime backs every local checkout and worktree, and in the cloud one per-user sandbox backs all your cloud workspaces. What moves through the lifecycle — create, set up, run, review, wrap up — is the workspace's checkout, not the runtime behind it. See lifecycle & storage for the full sequence.
Choose the right workspace type
You choose where a workspace runs when you create it, from the same picker used to start a new chat. This is the only place that choice lives.
| Target | Use it when |
|---|---|
| Local checkout | You want the agent to work directly in an existing repo. |
| New worktree | You want a clean branch and working tree for one reviewable stream of work. |
| Cloud | You want the agent to run remotely and keep working away from your laptop. |
Today a workspace stays on the target it was created with. To move the same branch somewhere else, publish it and open a new workspace against it there.
Find it in the sidebar
Every workspace shows up in the sidebar with an indicator for its target, and for whether it was created by you, an automation, or another agent.
What's inside
A single workspace holds:
- Agent sessions and chats.
- Terminals.
- A browser or preview surface, when the repo has a runnable app.
- The file browser, scoped to that checkout or sandbox.
- Git review and pull request status.
Worktrees isolate workflow and branch state. They are not a security boundary. Cloud workspaces isolate execution away from your laptop.
Go deeper
Connect a repo
Add a repository so Proliferate can create workspaces, branches, and reviewable diffs.
Local & cloud
Where local, worktree, and cloud workspaces actually execute, and what's shared versus isolated between them.
Parallel agents
Run agents side by side across workspaces, or delegate scoped work to subagents inside one.
Review & publish
Approve the plan, read the diff before it merges, and publish a branch or pull request.