Skip to main content
Conductor keeps the control plane in files. That makes the runtime inspectable, portable, and versionable with the repo.

What lives in conductor.yaml

The generated config typically holds:
  • port
  • boards
  • columnAliases
  • preferences
  • projects
  • defaults
  • plugins

Project-level control

Each project can define its own repo path, default agent, runtime, dev server, and MCP tools.

Practical guidance

  • Keep one project entry per repository root.
  • Use project-specific MCP servers when tooling differs between repos.
  • Treat conductor.yaml as operational source of truth, not generated trash.
  • Restart the running dashboard after major config changes if the UI looks stale.
Last modified on March 6, 2026