Sample settings configurations

Start with the smallest .conductor/settings.toml file that makes your project runnable. Add sections only when the project needs them.

Commit .conductor/settings.toml when the settings should travel with the project. Add .conductor/settings.local.toml to .gitignore for project overrides.

Minimal script-only example

Most repositories only need scripts at first:

"$schema" = "https://conductor.build/schemas/settings.repo.schema.json"

[scripts]
setup = "pnpm install"
run = "pnpm dev --port $CONDUCTOR_PORT"
run_mode = "concurrent"

Use this when:

• pnpm install prepares a fresh workspace.
• pnpm dev starts the app or server.
• The project can run multiple workspaces at once by using CONDUCTOR_PORT.

Use run_mode = "nonconcurrent" instead when the project depends on one fixed port, one local database, one Docker stack, or another shared resource.

More examples

What to add next

Add sections only when you need them:

• Add archive when archiving a workspace should clean up project-specific resources.
• Add file_include_globs when you need Conductor to copy gitignored files and you are not using .worktreeinclude.
• Add environment_variables when agents need repository-specific variables that should not come from the normal shell environment.
• Add prompts when the repository needs custom agent instructions.
• Add git settings when the repository should override Conductor's Git defaults.

For the full settings model, see User and project settings. For supported keys, see Settings reference.