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.js 18+ and pnpm (for UI)

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

(optional) Build UI (ui-next) and embed it in the server

./build_ui_next.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** (includes the ui-next UI):

UI at http://localhost:5000 | API at http://localhost:8080

docker run -p 5000:5000 -p 8080:8080 conductoross/conductor:next ```

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>

Conductor servers and workers scale independently. Use task domains, concurrency limits, persistence configuration, and metrics to match throughput and isolation to your environment. </details>

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

Yes. Conductor persists workflow and task state, supports recovery after worker and infrastructure failure, and exposes retries, timeouts, pause, resume, and termination controls. </details>

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

Conductor supports restart, rerun, and retry controls. Execution-history retention depends on configuration, and <code>keepLastN</code> intentionally removes older loop iterations. </details>

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

Yes. Conductor provides native LLM tasks, MCP tool discovery and calls, human approval, and vector workflows for RAG. See the maintained <a href="https://docs.conductor-oss.org/conductor/devguide/ai/llm-orchestration.html">LLM orchestration guide</a> for provider and capability details. </details>

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

Conductor keeps orchestration as a versioned, machine-readable graph while workers and built-in tasks perform business logic and side effects. This makes paths, inputs, policy, and task outcomes inspectable without constraining the language used for workers. </details>

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

JSON keeps the orchestration graph machine-readable and versioned. Workers remain ordinary code, and built-in tasks cover common integration and control-flow behavior. Use validated runtime definitions when a service or LLM needs to select an approved plan at runtime. </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>What does Conductor provide for adaptive agents?</strong></summary>

Conductor combines native AI and MCP tasks with durable loops, branches, fan-out, approval, retry, cancellation, and an inspectable execution history. Start with the <a href="https://docs.conductor-oss.org/conductor/devguide/ai/dynamic-workflows.html">governed adaptive graph</a>. </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>

---