Configuration
Per-repo setup, scripts, and defaults.
Repository configuration tells Proliferate how a repo should be prepared, started, and defaulted when agents create workspaces for it.
Use it to avoid repeating the same setup instructions in every workspace, and to keep local and cloud runs behaving the same way.
Find it under Settings → Repo, in three tabs: Configure, Actions, and Environment.
Local and Cloud are separate
Every repo has a Local side and a Cloud side, and each one keeps its own settings. Switch between them at the top of the repo's settings to edit whichever context you're configuring.
- Local settings apply to worktrees created on your machine.
- Cloud settings apply to workspaces that run on remote compute.
A setup script or run command you write for Local does not carry over to
Cloud, and vice versa. This lets a repo run pnpm install locally but a
container-friendly install step in the cloud, for example.
Configure: default branch
The Configure tab sets the default branch Proliferate uses as the base for new worktrees and pull requests.
- On Local, you can leave it on auto-detect, which follows your checkout's current branch, or pin it explicitly.
- On Cloud, you can leave it on the GitHub default branch or pick a different one from the repo's branch list.
Repo settings → Configure tab
Default branch selector for a repo, with the Local/Cloud context switch and the effective branch shown underneath.
Actions: setup script and run command
The Actions tab holds the two scripts that run around agent work in a workspace.
- Setup script: runs once when a new worktree or cloud workspace is
created. Use it to install dependencies, generate files, or otherwise get a
fresh checkout ready to work in. On Local, it has access to
PROLIFERATE_WORKTREE_DIR,PROLIFERATE_REPO_DIR,PROLIFERATE_BRANCH, andPROLIFERATE_BASE_REF. Proliferate can also detect common setup commands (likepnpm installorbundle install) from files in your repo and suggest them as one-click additions. - Run command: a single-line command launched by the workspace's Run button. Use it to start your app, service, or dev server.
Repo settings → Actions tab
Setup script editor and run command field for a repo, with detected setup command suggestions below the editor.
Good scripts are deterministic and safe to run unattended: they fail clearly, avoid destructive behavior, and work from a fresh checkout.
Environment: variables and secret files (cloud only)
The Environment tab stores environment variables and files that get synced into cloud workspaces for this repo. It's cloud-only: local workspaces just read whatever is already in your shell and checkout, so there's nothing to configure there.
Repo settings → Environment tab
Cloud secrets panel for a repo, listing environment variable and file names available to cloud workspaces (values are write-only).
See Secrets for how these are stored and who can read them.
What's configured elsewhere
A few things that sound like they belong here actually live in different settings, because they apply across every repo rather than to one:
- Agent and model defaults (which harness, such as Claude Code, Codex, OpenCode, or Grok, and which model new chats start with) live under Defaults.
- Review policy (plan review, code review, approvals) is configured per session and per organization, not per repo. See Review.
- Worktree cleanup (how many worktrees to keep per repo before Proliferate prunes old ones) lives under Settings → Pruning. See Connect a repository.