Use case
Open-source maintainers
Run issue and PR work through markdown boards without adopting a proprietary project-management SaaS.
Use Cases
Where Conductor fits in a real engineering workflow
Conductor is for teams that want markdown intake, repo-local control, visible runtime state, and agent routing without adopting a hosted orchestration product.
Use case
AI-heavy product teams
Dispatch multiple coding agents in parallel while keeping review state, CI, and runtime visibility in one local-first dashboard.
Use case
Consultancies and agencies
Keep each client repo isolated with project-level config, agent profiles, and repo-local conductor.yaml files.
Use case
Infrastructure and platform teams
Drive automation through MCP, webhooks, and terminal tooling instead of depending on a hosted workflow layer.
Best fit
Choose Conductor when the repo should stay in charge
- Boards live in markdown instead of a hosted planning product.
- Agent defaults, MCP servers, and project metadata belong in config files.
- Review, retry, worktrees, and tmux sessions need to stay inspectable.
Next step
Start with the operating model, not just the install
The fastest way to evaluate fit is to launch the browser-first flow, add one real repository, and run a task through dispatch, review, and retry.
Open getting started