Repo configuration

Repository configuration tells Proliferate how a repo should be prepared, started, and defaulted when agents create workspaces for it. Find it under Settings → Repo.

Every repo has a Local side and a Cloud side, and each keeps its own setup script, run command, and defaults. Switch between them at the top of the repo's settings.

Setup script and run command

The Actions tab holds the two scripts that run around agent work:

• Setup script — runs once per new worktree or cloud workspace, to install dependencies and get a fresh checkout ready:

  pnpm install

• Run command — a single-line command the workspace's Run button launches:

  pnpm dev

Both scripts get environment variables describing where they're running, and Proliferate can detect and suggest common setup commands from your repo. See Setup & action scripts for the full contract.

Secrets available to sessions

The Environment tab stores variables and files synced into cloud workspaces for this repo; local workspaces just read your existing shell and checkout. See Secrets for how these are stored and who can read them.

Defaults inherited by new workspaces

New workspaces for a repo start from the Configure tab's default branch. A couple of other things are easy to assume are repo settings but aren't:

• Default branch: on Local, auto-detect or a pinned branch; on Cloud, the GitHub default branch or another one you pick.
• Agent and model: chosen per session when you start one, not inherited from the repo. Org-wide default agent/model selection is planned but not built.
• Review policy: Plan mode and plan approval are a per-session choice — see Plan mode and plan approval. An org-wide review policy is also planned but not built.
• Worktree cleanup: how many worktrees to keep per repo before Proliferate prunes old ones, set under Settings → Pruning. See Pruning managed worktrees.