Connect a repo

Connect a repository so agents have real code to work against. It becomes the source for workspaces, branch names, setup scripts, terminals, previews, and review.

Add a repository

Open Add repository. There are three options:

• Link a local repo and Add a local repo both open your folder picker and register the folder as soon as you pick it. They do the same thing; take whichever label matches how you think about the repo.
• Add a cloud repo searches the GitHub repositories you can reach, or takes an owner/repo value directly.

A local repo confirms with Repository added and a Customize defaults shortcut. A cloud repo just shows a toast.

Local repo or cloud repo

Local works with any git checkout on your machine.

Cloud needs a GitHub-backed repo. Proliferate reaches it through its GitHub App, and sandboxes clone through that app rather than a personal access token. If the app is not authorized or not installed on the repo, the picker prompts you to fix that before it lists anything.

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 repository can be configured for both local and cloud, but each surface needs its own source:

• Local checkout — the folder you linked.
• Local worktrees — a branch and working tree per workspace, created from that checkout.
• Cloud base clone — one clone in your sandbox, used as the source for a worktree per cloud workspace.

You pick the target when you create a workspace, not when you connect the repo. Adding a repo from GitHub does not create a checkout on your machine, so link a local clone before you create local worktrees. See Local & cloud.

Configure the repo

Set the default branch, setup script, and run command before you create your first workspace.