Managed settings

Managed settings build on Conductor's normal user and project settings model. In that model, user settings provide personal defaults, repository shared settings define project behavior, and project overrides apply to one project on one machine.

Managed settings add one organization-controlled layer above that stack. They are for organizations that need to enforce selected Conductor settings on a user's Mac. Most users should configure user and project settings instead.

Managed values override user and repository settings, disable the matching controls in Settings, and are used when Conductor launches agents. Managed settings are provisional.

File location

Write managed TOML settings to:

~/.conductor/settings.managed.toml

Conductor still reads legacy ~/.conductor/settings.managed.json, but TOML is the recommended format.

Example

"$schema" = "https://conductor.build/schemas/settings.toml.json"
enterprise_data_privacy = true
claude_code_executable_path = "/opt/homebrew/bin/claude"

[models]
default = "gpt-5.5"

[environmentVariables.local]
ANTHROPIC_BASE_URL = "https://api.example.com"

[environmentVariables.cloud]
OPENAI_BASE_URL = "https://openai.example.com"

Settings reference

For the managed key list, see Settings reference.

Precedence

Managed settings have the highest precedence. When a managed file defines a supported setting, it overrides the normal settings stack:

1. Managed settings.
2. Project overrides.
3. Repository shared settings.
4. User shared settings.
5. Built-in defaults.

For the full settings precedence model, see User and project settings.