Step-level File Piping In Workflows

The single biggest friction in modern workflow design is forcing every step to manually inject file content into commands via shell hacks. Instead of wrestling with quotes and cat, a dedicated input: field would pipe real data straight to stdin - clean, safe, and intuitive. Consider this: input: ${fetch.stdout} | command replaces messy shell glue with semantic clarity. This isn’t just a nicety; it’s a lifeline for reliable data flow. In practice, teams skip quotes on paths with spaces, avoid shell injection risks, and keep dependencies explicit. But here’s the blind spot: most tools still treat input as a script residue, not a first-class design element. The real challenge? Making the DAG editor feel natural, not like a terminal script lab. The bottom line: when input handling is built into the step layer, workflows breathe easier - and so do developers.