feat: add wac ai context for frontend chat (#9021)

* feat: add wac ai context

* fix: limit wac context languages

* fix: pass wac auto kind in flow script drawer
This commit is contained in:
centdix
2026-05-05 15:00:06 +00:00
committed by GitHub
parent 4ba46c0e1c
commit 0d0557fc9d
19 changed files with 203 additions and 41 deletions
+3 -3
View File
@@ -6165,12 +6165,12 @@ Use this guide when writing or modifying Windmill Workflow-as-Code (WAC) scripts
WAC is authored as a Windmill script and deployed with the normal script workflow. It is not an OpenFlow YAML flow.
Supported WAC authoring targets:
- TypeScript scripts that import from \`windmill-client\`
- Bun TypeScript scripts that import from \`windmill-client\`
- Python 3 scripts that import from \`wmill\`
## File Shape
TypeScript:
Bun TypeScript:
\`\`\`typescript
import {
@@ -6212,7 +6212,7 @@ async def main(x: str):
Rules:
- Do not call \`main\`.
- TypeScript should export the workflow entrypoint, preferably \`export const main = workflow(async (...) => { ... })\`.
- Bun TypeScript should export the workflow entrypoint, preferably \`export const main = workflow(async (...) => { ... })\`.
- Python must use \`@workflow\` on an async top-level function, usually \`main\`.
- Define task functions and \`taskScript\`/\`task_script\` or \`taskFlow\`/\`task_flow\` assignments at module top level with stable names.
- Use the exact SDK names. Do not alias \`workflow\`, \`task\`, \`taskScript\`, \`taskFlow\`, \`step\`, \`sleep\`, \`waitForApproval\`, \`task_script\`, \`task_flow\`, or \`wait_for_approval\`; the WAC parser recognizes these names directly.