feat: add shell step type for running commands in flows#5
Open
ChicK00o wants to merge 13 commits into
Open
Conversation
- Add shell step as Step Type 6 with full reference table, when-to-use comparison table vs agent steps, and common patterns (build, test, lint, migration) - Add 'command' to the step type inference table - Add shell step rule to Important Rules section
ChicK00o
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Flows had no way to run arbitrary shell commands as steps. Every step required an AI agent, even for simple operations like running a build, executing a test suite, or calling a CLI tool. This forced users to wrap trivial shell commands in agent prompts, wasting model calls and adding latency.
What was fixed
shellstep type that runs a command viash -cwith configurable timeout andon_complete/on_errorrouting.pi/flows/config.yaml→ flow-levelconfig:→ per-stepconfig:) so commands can reference${{config.key}}without hardcoding values${{config.key}}template variable support toexpandTemplateVariables${{result.STEP.output}}— stdout was stored only asfullOutput, so the documented variable resolved to empty string; now stored as typed outputoutput(andstderr) so downstream steps can read shell output correctlyclosehandler