Build durable workflow workers and Conductor agents with JavaScript/ TypeScript. These guides cover OSS and Orkes; pages call out capabilities that require Orkes.
| Goal | Guide | Expected result |
|---|---|---|
| Connect to a server | Server setup and connection/authentication | The SDK can reach an OSS or Orkes API endpoint. |
| Build a workflow and worker | Core quickstart | The hello-world workflow prints its result. |
| Build a Conductor agent | Agent quickstart | An LLM-backed agent completes through Conductor. |
- Workflows, workflow lifecycle, and workers
- Workflow testing, schemas, schedules/events, and the workflow message queue
- Conductor agents, tools, and framework bridges
- Recommended examples; examples/README.md is the full catalog.
- Core API map, compatibility, and upgrading
- One reference page per client in docs/api-reference/ (
application-client.md,task-client.md,workflow-executor.md, ...) - Agent runtime, control plane, and agent definition
- Lease extension / heartbeat for long-running workers
- Java/Python documentation parity — intentional JS mappings, JS-only pages, and unsupported Java/Python-only surfaces
Primary guides follow the documentation standard.
Provider credentials belong on the Conductor server or its secret provider,
not in workflow input, example source, or a client-side .env committed to
Git.