Multi-Repo and Sessions

Operate parallel work across several repositories without losing isolation or review clarity.

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.