Repo configuration

Repository configuration tells Proliferate how to prepare and start a repo when agents create workspaces for it. It lives under Settings → Repo.

Each repo carries its own setup script, run command, and defaults.

Setup script and run command#

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

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

  sh

  pnpm install

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

  sh

  pnpm dev

Both get environment variables describing where they are running, and Proliferate can suggest setup commands it detects in your repo. See Setup & action scripts.

Secrets available to sessions#

The Environment tab stores the variables and files this repo needs. Local workspaces also 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 start from the default branch on the Configure tab. A few things look like repo settings but are not:

• Default branch: auto-detect, or a branch you pin.
• 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. 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.