Connect a repo

Connect a repository when you want agents to work against real code.

The repository becomes the source for workspace creation, branch naming, setup scripts, terminals, browser previews, and review.

Add a repository

Open Add repository and pick one of three options:

• Link a local repo or Add a local repo: both open your machine's folder picker and register the folder the moment you pick it. There's no extra confirmation step, and no functional difference between the two — pick whichever description matches how you think about the repo.
• Add a cloud repo: search the GitHub repositories you can access, or paste an owner/repo value directly, to run the repo in your cloud sandbox.

Adding a local repo shows a Repository added confirmation with a Customize defaults shortcut into that repo's settings. Adding a cloud repo skips the confirmation — you're usually about to open a cloud workspace right away — and just shows a toast.

Local repo or cloud repo

Local options work with any Git checkout already on your machine. Cloud needs a GitHub-backed repo: Proliferate reaches your repositories through its GitHub App, and cloud sandboxes clone through that app instead of a personal access token. If the app isn't authorized for your account or installed on the repo, the cloud picker shows an inline prompt to fix that before it lists repositories.

Org admins manage that installation from org settings. Self-hosted deployments create their own app as part of the cloud sandboxes add-on, which is coming soon.

One repo, several running copies

The same GitHub repository can have Local and Cloud configuration, but each execution surface needs its own source:

• Local checkout: the folder you linked on your machine.
• Local worktrees: a separate branch and working tree per workspace, created from that linked checkout.
• Cloud base clone: one repository clone in your personal cloud sandbox, reused as the source for separate managed worktrees. Every cloud workspace gets its own worktree and branch; cloud workspaces do not all edit the base clone.

You choose the target when you create a workspace, not when you connect the repo. A repo linked locally can also get Cloud configuration and a cloud base clone. A repo added from GitHub for Cloud does not create a checkout on your machine; link a local clone of that repository before creating local worktrees. See Local & cloud for how the two targets differ.

Configure the repo

Before you create your first workspace, set the repo's default branch, setup script, and run command, once for local work and once for cloud work.