Get started
Quickstart
Choose how you want to run Proliferate, create a workspace, and review your first agent run.
Use this path to get from a fresh install to reviewable agent work.
1. Decide on your hosting type
Start with the deployment model that matches your team:
- Hosted when you want to try Proliferate quickly. Download the desktop app and sign in; there is no server to run.
- Self-hosted when agent execution, code, credentials, and the state of the control plane (the server that coordinates workspaces and accounts) need to stay inside your own cloud account or VPC.
Most teams start hosted and move to self-hosted later if they need to. This is a decision about where your Proliferate account and data live, not where an individual workspace runs; you choose local or cloud for each workspace separately in the next step.
2. Create a new repo workspace
Add a repository and create a workspace for the task you want an agent to run. A workspace carries the repository, branch state, terminals, browser previews, files, and review surface for one stream of work.
When you create it, pick where the workspace runs: a local checkout, a new worktree, or a cloud workspace. For most code changes, start with a new worktree or cloud workspace so the agent works away from your main checkout.
This choice is fixed for the life of the workspace. To continue the same work on the other target later, publish the branch from the current workspace and open a new one for it there.
New workspace dialog
Repository picker with Local checkout, New worktree, and Cloud workspace target options.
3. Use our agents or yours
Pick the agent you want for the job. Proliferate can run built-in/default agent paths, or it can launch the coding agents your team already uses.
Agent support includes:
Advanced routing, proxies, and organization-wide agent defaults live in advanced agent settings.
Agent picker in the chat composer
Harness selector alongside model, mode, and permission controls for the session about to start.
4. Review your work
When the run finishes, review the workspace as a diff and an execution history. Check the files, branch state, command output, tests, and any generated pull request before integrating.
Developers stay responsible for direction and quality. Agents take on bounded implementation work inside workspaces you can inspect.
Workspace review panel
Git diff view of unstaged changes with a publish action for opening a pull request.
5. Explore
Once the first workspace feels solid, try the rest of the platform:
- Workspaces for connected repo environments.
- Workflows for recurring and on-demand agent work.
- Integrations for pre-registered tools.
- Configure Proliferate for secrets, defaults, preferences, and admin settings.