Your first workspace

A workspace is where Proliferate runs repository-backed code work.

Use a workspace when the result should be tied to a GitHub repository, branch, diff, test run, or pull request. Use Cowork when you want to start from a thread, plan, artifact, or higher-level coordination.

Add a GitHub repository

After installing Proliferate, add a repository you want agents to work in.

Proliferate manages the repository as a source for workspaces. Each workspace you create will get its own branch, working tree, sessions, files, and review state.

Configure your workspaces

You can configure how workspaces for a given repo should run- setup scripts for dependencies, run scripts for your app, and cloud settings for remote execution. See Workspaces for the deeper model.

Create a local, worktree, or cloud workspace

When you start work from a repository, choose where it should run.

You can migrate workspaces from cloud environments to local checkouts and vice versa at any point.

For your first workspace, choose New worktree unless you specifically want the agent to work in your current checkout or in the cloud.

Do work

Once the workspace opens, use it as the working surface for the task.

Inside a workspace, you can use:

• Multiple chats or agent sessions.
• Terminals for commands, tests, and app output.
• Browser or preview surfaces when the repo has a runnable app.
• File browser and git views for inspecting changes.
• Pull request review surfaces when the branch is ready.

Clean up

When the workspace's PR is merged, close the loop by getting the worktree off your machine. You have two options:

• Let Proliferate clean it up. Proliferate will auto-detect a merged branch and non-destructively archive your workspace on its own. You can configure this in Settings → Workspaces → Auto-clean merged worktrees.
• Clean it up yourself. Mark the workspace as done and delete it. Proliferate removes the worktree directory and archives the workspace state.

Go deeper

Next: start your first Cowork task.