Preferences

Tune local Proliferate behavior for your own workflow.

Preferences are personal settings for how Proliferate feels day to day. They live under Settings → User, in the General and Appearance sections, plus Pruning for local worktree cleanup.

General

Screenshot: Settings > User > General

The General preferences page, showing the default-open-in picker, git branch prefix, new-workspace mode, paste-to-attachment toggle, turn-end sound, and session-policy switches.

PreferenceWhat it does
Default open inWhich app the workspace's Open in button launches (your editor, Finder, or Terminal).
Git branch prefixPrefix applied to auto-generated branch names: none, proliferate/..., or your GitHub username.
New workspaceWhat ⌘N creates by default: a new worktree, or the repo opened locally.
Turn long pastes into attachmentsConverts large pasted text into a file attachment in the composer instead of an inline block.
Turn end soundPlays a sound when an agent finishes its turn.
Allow coding agents to spin up subagentsApplies to new sessions only; existing sessions keep the delegation policy they started with.
Allow cowork agents to create coding workspacesApplies to new cowork sessions only, same rule as above.

Appearance

Screenshot: Settings > User > Appearance

The Appearance page, showing the light/dark/system mode switcher, a live diff preview, window zoom control, font size pickers, and the transparent chrome toggle.

PreferenceWhat it does
ModeLight, dark, or follow the system setting.
Window zoomZooms the entire window, like browser zoom. Independent of the font size settings below.
UI font sizeScales app and chat text.
Code font sizeScales editors, diffs, and code blocks.
Transparent chromeApplies a glass treatment to workspace headers and tab bars.

Pruning

Screenshot: Settings > User > Pruning

The Pruning page, showing worktree storage usage and controls to prune stale local checkouts.

Review how much disk space local worktrees are using and prune the ones you no longer need.

Organization-wide behavior, including which agents and auth routes members may use, belongs to an admin and is covered in Allowed harnesses and Admin settings.

On this page