A CLI tool for defining and running multi-agent workflows with the GitHub Copilot SDK and Anthropic Claude.
A single LLM prompt can answer a question, but it can't review its own work, research from multiple angles, or pause for human approval. You need multi-agent workflows—but building them means coding custom solutions, managing state, handling failures, and hoping you don't create infinite loops.
Conductor provides the patterns that work: evaluator-optimizer loops for iterative refinement, parallel execution with failure modes, and human-in-the-loop gates. Define them in YAML with built-in safety limits. Version control your workflows like code.
- YAML-based workflows - Define multi-agent workflows in readable YAML
- Multiple providers - GitHub Copilot or Anthropic Claude with seamless switching
- Parallel execution - Run agents concurrently (static groups or dynamic for-each)
- Script steps - Run shell commands and route on exit code without an AI agent
- Conditional routing - Route between agents based on output conditions
- Human-in-the-loop - Pause for human decisions with Rich terminal UI
- Safety limits - Max iterations and timeout enforcement
- Web dashboard - Real-time DAG visualization with agent detail streaming
- Validation - Validate workflows before execution
# Install from GitHub
uv tool install git+https://github.com/microsoft/conductor.git
# Run the CLI
conductor run workflow.yaml
# Or run directly without installing
uvx --from git+https://github.com/microsoft/conductor.git conductor run workflow.yaml
# Install a specific branch, tag, or commit
uv tool install git+https://github.com/microsoft/conductor.git@branch-name
uv tool install git+https://github.com/microsoft/conductor.git@v1.0.0
uv tool install git+https://github.com/microsoft/conductor.git@abc1234pipx install git+https://github.com/microsoft/conductor.git
conductor run workflow.yaml
# Install a specific branch or tag
pipx install git+https://github.com/microsoft/conductor.git@branch-namepip install git+https://github.com/microsoft/conductor.git
conductor run workflow.yaml
# Install a specific tag or commit
pip install git+https://github.com/microsoft/conductor.git@v1.0.0# my-workflow.yaml
workflow:
name: simple-qa
description: A simple question-answering workflow
entry_point: answerer
agents:
- name: answerer
model: gpt-5.2
prompt: |
Answer the following question:
{{ workflow.input.question }}
output:
answer:
type: string
routes:
- to: $end
output:
answer: "{{ answerer.output.answer }}"conductor run my-workflow.yaml --input question="What is Python?"{
"answer": "Python is a high-level, interpreted programming language..."
}Conductor supports multiple AI providers. Choose based on your needs:
| Feature | Copilot | Claude |
|---|---|---|
| Pricing | Subscription ($10-39/mo) | Pay-per-token |
| Context Window | 8K-128K tokens | 200K tokens |
| Tool Support (MCP) | Yes | Planned |
| Streaming | Yes | Planned |
| Best For | Heavy usage, tools | Large context, pay-per-use |
workflow:
runtime:
provider: claude
default_model: claude-sonnet-4.5Set your API key: export ANTHROPIC_API_KEY=sk-ant-...
See also: Claude Documentation | Provider Comparison | Migration Guide
Execute a workflow from a YAML file.
conductor run <workflow.yaml> [OPTIONS]| Option | Description |
|---|---|
-i, --input NAME=VALUE |
Workflow input (repeatable) |
-p, --provider PROVIDER |
Override provider |
--dry-run |
Preview execution plan |
--skip-gates |
Auto-select at human gates |
--web |
Start real-time web dashboard |
--web-bg |
Run in background, print dashboard URL, exit |
--web-port PORT |
Port for web dashboard (0 = auto) |
-q, --quiet |
Suppress progress output |
-s, --silent |
Suppress all output except errors |
-l, --log-file PATH |
Write logs to file |
Validate a workflow file without executing.
conductor validate <workflow.yaml>Create a new workflow from a template.
conductor init <name> --template <template> --output <path>List available workflow templates.
conductor templatesFull CLI documentation: docs/cli-reference.md
See the examples/ directory for complete workflows:
| Example | Description |
|---|---|
| simple-qa.yaml | Basic single-agent Q&A |
| for-each-simple.yaml | Dynamic parallel processing |
| parallel-research.yaml | Static parallel execution |
| design-review.yaml | Human gate with loop pattern |
| script-step.yaml | Script step with exit_code routing |
More examples and running instructions: examples/README.md
| Document | Description |
|---|---|
| Workflow Syntax | Complete YAML schema reference |
| CLI Reference | Full command-line documentation |
| Parallel Execution | Static parallel groups |
| Dynamic Parallel | For-each groups and array processing |
| Claude Provider | Claude setup and configuration |
| Provider Comparison | Copilot vs Claude decision guide |
- Python 3.12+
- uv for dependency management
git clone https://github.com/microsoft/conductor.git
cd conductor
make devOn Windows, use uv directly instead of make:
uv sync --all-extras # instead of make dev
uv run pytest tests/ # instead of make test
uv run ruff check . # instead of make lint
uv run ruff format . # instead of make formatCopilot CLI path: Windows subprocess cannot resolve .bat/.ps1 wrappers by name alone. If you see [WinError 2] The system cannot find the file specified when running workflows, set the full path to the Copilot CLI:
# Find your copilot CLI
Get-Command copilot* | Format-Table Name, Source
# Set the path (use the .cmd variant from npm)
$env:COPILOT_CLI_PATH = "C:\Users\<you>\AppData\Roaming\npm\copilot.cmd"make test # Run tests
make test-cov # Run tests with coverage
make lint # Check linting
make format # Auto-fix and format code
make typecheck # Type check
make check # Run all checks (lint + typecheck)
make validate-examples # Validate all example workflowsThis project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit Contributor License Agreements.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
To submit a pull request, follow these steps:
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Make your changes
- Run tests and checks (
make test && make check) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
MIT License - see LICENSE for details.