Introducing Conductor Cloud →Skip to docs content

Reference

Settings

Reference for Conductor account, model, provider, repository, and app settings

Settings control how Conductor runs agents, repositories, scripts, and app behavior on your Mac.

Managed settings

Managed settings are provisional. Organizations can manage selected settings by writing ~/.conductor/settings.json on a user's Mac.

Managed values override local database settings, disable the matching controls in Settings, and are used when Conductor launches agents.

Use the published schema for editor autocomplete and validation. You can also point an agent to https://conductor.build/schemas/settings.json so it can fetch the supported managed settings:

{
    "$schema": "https://conductor.build/schemas/settings.json",
    "enterpriseDataPrivacy": true,
    "claudeExecutablePath": "/opt/homebrew/bin/claude",
    "defaultModel": "gpt-5.5"
}

Supported managed settings:

SettingTypeDescription
enterpriseDataPrivacybooleanEnables Enterprise data privacy.
claudeExecutablePathstringOverrides the Claude Code executable path.
defaultModelstringSets the default model. Supported values are defined by the JSON Schema.

Account

Use Account settings for sign-in, privacy controls, and account-level preferences. Privacy-sensitive behavior is also covered in Privacy.

Models

Use Models settings to choose which Claude Code and Codex models appear in the model picker. Some model-specific controls, such as thinking or reasoning level, are configured per session.

Providers

Use Providers settings to configure model providers such as Anthropic-compatible providers, Bedrock, Vertex, OpenRouter, or Vercel AI Gateway.

For setup examples, see Configure model providers.

Repositories

Repository Settings control behavior for one repository:

  • Workspace path
  • Files to copy into new workspaces
  • Git remote behavior
  • Setup, run, and archive scripts
  • Shared conductor.json configuration
  • Code review preferences
  • Create PR preferences
  • Fix errors preferences
  • Resolve conflicts preferences
  • Branch rename preferences
  • General preferences

Use repository preferences for instructions that should apply every time an agent works in that repository.

For file-copy pattern behavior, see Files to copy.

Git

Git settings control how Conductor interacts with local branches, remotes, pull requests, and related GitHub flows.

Appearance and storage

Appearance settings control UI preferences. Storage settings help you inspect or manage local Conductor data.

Experimental

Experimental settings expose features that are still changing. Documentation for experimental behavior may be narrower than documentation for stable features.

Big Terminal Mode is enabled from Experimental settings. For behavior and shortcuts, see Big Terminal Mode.

On this page