Skip to main content
Real teams often need a task to cross repository boundaries. Conductor should make that visible without collapsing everything into one noisy runtime.

​
Where multi-repo helps

  • frontend and backend pairs
  • service-to-service changes
  • platform rollouts
  • monorepo split workflows

​
Keep the isolation boundary clear

Every task still needs a defined worktree, prompt trail, and review path. Multi-repo support is valuable only if it preserves that clarity.
Last modified on March 6, 2026