Files
windmill/backend
Ruben FiszelandClaude Opus 5 525ce44c75 wip: run workflow-as-code rounds on a bun dedicated worker
Prototype. The dedicated wrapper gains a WAC runner: it rebuilds a `WorkflowCtx`
from the round's checkpoint, invokes the `workflow()` entrypoint, and reports the
resulting `WacOutput` as `wm_res[wac]:`, which the worker feeds to
`handle_wac_v2_output`.

`task()` name injection has to happen here too — step keys come from the variable
a task is assigned to and address the checkpoint, so skipping it would name every
step differently from what the per-job executor produces for the same source.

windmill-client is imported only when a registered script is a workflow: a plain
dedicated script need not have it installed at all.

Measured on a two-worker local EE backend, mean of 5 runs, wall clock:

  sequential workflow, trivial startup    281 ms dedicated / 300 ms regular
  parallel + inline step + caught failure 287 ms dedicated / 298 ms regular
  sequential, ~200ms module init          275 ms dedicated / 1017 ms regular

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VMNiDoBuUY9jzqcuFLT2wU
2026-08-22 08:10:51 +00:00
..
…
…
…
…
…
…
…
…
…

Windmill Backend

This folder holds all backend components, the src/ folder only contains files used to build the "root" binary.

Components

name description
windmill-api The API server, exposing functionality to other components and the frontend
windmill-audit Contains audit functionality, allowing different components to record important actions
windmill-common Common code shared by all crates
windmill-queue Contains job & flow queuing functionality, commonly written to by the API server and read from by workers
windmill-worker The worker. Used to process and execute flows & jobs.
parsers Contains code to parse signatures in different langauges.

Compile sqlx for offline ci

cargo sqlx prepare --workspace -- --bin windmill --features enterprise