dagu

DAG Authoring

Load only the reference file that matches the task.

Default Approach

• Prefer type: graph for new DAGs. It supports both sequential flow via depends: and parallel flow.
• Prefer id on every step. Omit name unless the display label must differ from the step ID.
• Prefer dagu enqueue over dagu start for agent-run workflows.
• Prefer dagu schema ... and dagu validate ... over guessing field names or shapes.
• Prefer type: template when generating text files, prompts, or artifacts instead of assembling them with shell echo or heredocs.
• Prefer DAG_RUN_ARTIFACTS_DIR for file outputs when possible, as it provides a preview in the UI and automatically cleans up when the DAG run gets deleted.
• Prefer string-form output: VAR_NAME for capturing small stdout values into flat variables.
• Prefer object-form output: when downstream steps need structured values via ${step_id.output.*}.
• Prefer temporary file in artifacts dir for larger outputs or when downstream steps need file paths.

High-Signal Rules

• output: has two modes:
  • string form captures trimmed stdout into a flat variable such as ${VERSION}