Share repository settings with teammates
Commit .conductor/settings.toml so a repository can share Conductor scripts and settings
By default, Repository Settings apply only on your machine. To share scripts and other repository settings with teammates, commit a .conductor/settings.toml file in the repository.
Shared repository settings are useful for:
- Setup, run, and archive scripts.
- Run script mode.
- Enterprise data privacy.
- Spotlight testing.
- Repository action prompts.
- Provider and Git behavior that should apply to the whole team.
Step 1: Create the file
Create .conductor/settings.toml at the repository root.
"$schema" = "https://conductor.build/schemas/settings.repo.schema.json"
[scripts]
setup = "pnpm install"
run = "pnpm dev --port $CONDUCTOR_PORT"
run_mode = "concurrent"Adjust the commands for your project. Setup, run, and archive scripts run from each workspace directory, not from the original repository checkout.
Step 2: Commit it
Commit .conductor/settings.toml to the repository:
git add .conductor/settings.toml
git commit -m "Add Conductor repository settings"
git pushIf you create .conductor/settings.local.toml for per-machine repository settings, add it to .gitignore from the repository root:
touch .gitignore
grep -qxF ".conductor/settings.local.toml" .gitignore || printf "\n.conductor/settings.local.toml\n" >> .gitignoreStep 3: Pull it in other workspaces
After teammates pull the commit, Conductor reads the shared settings for that repository. If a teammate has the same setting configured locally in .conductor/settings.local.toml, their local value wins.
Example: scripts and privacy
"$schema" = "https://conductor.build/schemas/settings.repo.schema.json"
enterprise_data_privacy = true
[scripts]
setup = "pnpm install"
run = "pnpm dev --port $CONDUCTOR_PORT"
archive = "./script/workspace-archive.sh"
run_mode = "concurrent"Use run_mode = "nonconcurrent" when the project depends on a fixed port, one local database, one Docker stack, or another shared resource that multiple workspaces cannot use at the same time.
Legacy conductor.json
Older repositories may still have conductor.json at the repository root. New shared settings should use .conductor/settings.toml. Once .conductor/settings.toml exists for a repository, Conductor ignores repo-level conductor.json.
For complete copyable files, see Sample settings configurations. For precedence and file locations, see User and project settings. For supported keys, see Settings reference. For script behavior, see Scripts.