Install Skills for Claude Code

/plugin marketplace add conductor-oss/conductor-skills /plugin install conductor@conductor-skills ```

Install for all detected agents

One command to auto-detect every supported agent on your system and install globally where possible. Re-run anytime — it only installs for newly detected agents.

macOS / Linux

curl -sSL https://conductor-oss.github.io/conductor-skills/install.sh | bash -s -- --all

Windows (PowerShell) / (cmd) ```powershell

Build From Source

<details> <summary><strong>Requirements and instructions</strong></summary>

Requirements: Docker Desktop, Java (JDK) 21+, Node 18 (for UI)

```shell git clone https://github.com/conductor-oss/conductor cd conductor ./gradlew build

(optional) Build UI

./build_ui.sh

Create a workflow that calls an API and parses the response — no workers needed

curl -s https://raw.githubusercontent.com/conductor-oss/conductor/main/docs/quickstart/workflow.json -o workflow.json conductor workflow create workflow.json

> **Note:** Running this command twice will return an error on the second call — the workflow already exists. This is expected behavior. Use `conductor workflow update` to modify an existing workflow.

See the [Quickstart guide](https://docs.conductor-oss.org/quickstart/) for the full walkthrough, including writing workers and replaying workflows.

**Docker Image for Conductor:**

All CLI commands have equivalent cURL/API calls. See the Quickstart for details.

---

SDKs

---

Why Conductor is the workflow engine of choice for developers

FAQ

<details> <summary><strong>Is this the same as Netflix Conductor?</strong></summary>

Yes. Conductor OSS is the continuation of the original Netflix Conductor repository after Netflix contributed the project to the open-source foundation. </details>

<details> <summary><strong>Is Conductor open source?</strong></summary>

Yes. Conductor is a fully open-source workflow engine licensed under Apache 2.0. You can self-host on your own infrastructure with 5 persistence backends and 6 message brokers. </details>

<details> <summary><strong>Is this project actively maintained?</strong></summary>

Yes. Orkes is the primary maintainer and offers an enterprise SaaS platform for Conductor across all major cloud providers. </details>

<details> <summary><strong>Can Conductor scale to handle my workload?</strong></summary>

Yes. Built at Netflix, battle-tested at internet scale. Conductor scales horizontally across multiple server instances to handle billions of workflow executions. </details>

<details> <summary><strong>Does Conductor support durable execution?</strong></summary>

Yes. Conductor pioneered durable execution patterns, ensuring workflows and durable agents complete reliably despite infrastructure failures or crashes. Every step is persisted and recoverable. </details>

<details> <summary><strong>Can I replay a workflow after it completes or fails?</strong></summary>

Yes. Conductor preserves full execution history indefinitely. You can restart from the beginning, rerun from a specific task, or retry just the failed step — via API or UI. </details>

<details> <summary><strong>Can Conductor orchestrate AI agents and LLMs?</strong></summary>

Yes. Conductor provides native integration with 14+ LLM providers (Anthropic, OpenAI, Gemini, Bedrock, and more), MCP tool calling, function calling, human-in-the-loop approval, and vector database integration for RAG. </details>

<details> <summary><strong>Why does Conductor separate orchestration from code?</strong></summary>

Coupling orchestration logic with business logic forces developers to maintain determinism constraints manually — no direct I/O, no system time, no randomness in workflow definitions. Conductor eliminates this entire class of bugs by making the orchestration layer deterministic by construction. Workers are plain code with zero framework constraints — write them in any language, use any library, call any API. </details>

<details> <summary><strong>Isn't writing workflows as code more powerful than JSON?</strong></summary>

It depends on what you mean by "powerful." In code-first engines, the workflow definition and your business logic live in the same runtime — which means the engine must replay your code to recover state. That forces determinism constraints on your business logic: no direct I/O, no system time, no threads, no randomness. Conductor separates these concerns. The orchestration graph is declarative (JSON), so it's deterministic by construction. Your workers are plain code with zero constraints — use any language, any library, call any API. You get the full power of code where it matters (business logic) without the framework tax where it doesn't (orchestration). </details>

<details> <summary><strong>Can JSON workflows handle complex logic like branching, loops, and error handling?</strong></summary>

Yes. Conductor supports SWITCH (conditional branching), DO_WHILE (loops with configurable iteration cleanup), FORK_JOIN (parallel execution with dynamic fanout), SUB_WORKFLOW (composition), and DYNAMIC tasks resolved at runtime. These are composable — you can nest loops inside branches inside forks. For error handling, every task supports configurable retries, timeouts, and optional/compensating tasks. The declarative model doesn't limit complexity — it makes complexity visible and debuggable. </details>

<details> <summary><strong>How does Conductor handle workflow versioning?</strong></summary>

Workflow definitions are versioned by number. Running executions continue on the version they started with — deploying a new version never breaks in-flight workflows. There's no replay compatibility problem because Conductor doesn't replay your code. The orchestration graph is the source of truth, and each execution is pinned to its definition version. Update orchestration logic without redeploying workers and without worrying about breaking running workflows. </details>

<details> <summary><strong>What about developer experience — IDE support, type checking, debugging?</strong></summary>

Conductor provides a built-in visual UI for designing, running, and debugging workflows. Every execution is fully observable: you can inspect the input, output, timing, and retry history of every task. For type safety, Conductor validates workflow inputs and task I/O against JSON Schema. Workers are plain code in your language of choice — you get full IDE support, type checking, and debugging for your business logic. The orchestration layer is visible in the UI, not hidden inside a framework. </details>

<details> <summary><strong>Can Conductor handle long-running workflows (days, weeks, months)?</strong></summary>

Yes. Conductor is designed for long-running workflows. Executions are fully persisted — a workflow can pause for months waiting for a human approval, an external signal, or a scheduled timer, and resume exactly where it left off. There's no in-memory state to lose. This is the same mechanism that makes AI agent loops durable: if iteration 12 waits for a human review for three weeks, iteration 13 picks up right where it left off. </details>

<details> <summary><strong>Don't I lose flexibility by not having orchestration in code?</strong></summary>

You gain flexibility. Because workflows are JSON, LLMs can generate and modify them at runtime — no compile/deploy cycle. Dynamic forks let you fan out to a variable number of parallel tasks determined at runtime. Dynamic sub-workflows let one workflow compose others by name. And because workers are decoupled from orchestration, you can update the workflow graph or swap worker implementations independently. Code-first engines couple these together, so changing orchestration means redeploying and re-versioning your code. </details>

<details> <summary><strong>How does Conductor compare to other workflow engines?</strong></summary>

Conductor is an open-source workflow engine with native LLM task types for 14+ providers, built-in MCP integration, durable execution, full replayability, and 7 language SDKs. Unlike code-first engines, Conductor separates orchestration from business logic — determinism is an architectural guarantee, not a developer constraint. Your workers are plain code with zero framework rules. The orchestration layer is declarative, so it's observable, versionable, and composable by LLMs. Battle-tested at Netflix, Tesla, LinkedIn, and J.P. Morgan. </details>

<details> <summary><strong>Is Orkes Conductor compatible with Conductor OSS?</strong></summary>

100% compatible. Orkes Conductor is built on top of Conductor OSS with full API and workflow compatibility. </details>

---