conductor-oss/conductor
Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents
What it solves
Conductor is a durable execution platform designed to manage complex, long-running workflows and AI agents. It prevents the loss of state during crashes, network failures, or restarts by persisting every step of an execution. It decouples the orchestration logic (the "graph") from the actual business logic (the workers), allowing developers to change the workflow's path without redeploying the worker code.
How it works
Workflows are defined as declarative, machine-readable JSON graphs. These graphs govern the sequence of tasks, including loops, branching, fan-out, and human approvals. Workers are polyglot—written in any language (Java, Python, Go, etc.)—and poll the server for tasks to execute and report results back. For AI agents, Conductor provides native LLM tasks and MCP (Model Context Protocol) tool discovery and calling, enabling agents to reason and act in durable loops.
Who it’s for
It is built for developers and operators who need to build scalable, reliable microservices orchestration or autonomous AI agents that require auditability, versioning, and the ability to recover from failures.
Highlights
- Durable Execution: Every step is persisted, ensuring workflows survive infrastructure failures with configurable retries and timeouts.
- AI Agent Orchestration: Native support for LLM chat completion, MCP tool calling, and vector workflows for RAG.
- Polyglot Workers: Support for workers written in Java, Python, Go, JavaScript, C#, Ruby, or Rust.
- Explicit Orchestration: Workflows are versioned JSON graphs, making the execution path inspectable and modifiable at runtime without code changes.
- Execution Recovery: Ability to restart, rerun, retry, pause, resume, or terminate specific executions based on policy.
Related
- Project
- Project
- Project
- Project
- Project