Steps
A step is a unit of work in a workflow. Gump has four kinds of steps, inferred from the fields you set — there’s no explicittype: field.
Agent Step
A step with anagent field. Runs a coding agent in the worktree.
name— unique identifier (required)agent— which agent to use (required)prompt— the prompt template, as a string orfile: pathoutput— what the agent produces:diff(default),plan,artifact,reviewcontext— additional context sources (file:,bash:)session— session mode:fresh(default),reuse,reuse-on-retry,reuse: <step>timeout— kill after this duration (e.g.,"5m")max_budget— cost limit for this step in dollarshitl— pause for human validation after executionguard— live breakers during executiongate— checks after executionon_failure— what to do if a gate or guard fails
Gate Step
A step withgate but no agent, steps, or workflow. Runs deterministic checks on the worktree without calling any agent.
on_failure applies (if present), otherwise the run stops.
Orchestration Step
A step with childsteps. Groups sub-steps together, optionally with foreach or parallel.
name, steps, foreach, parallel, gate, on_failure. An orchestration step can have its own gate and on_failure — if the group gate fails, the entire group retries.
Workflow Step
A step withworkflow but no agent or steps. Calls another workflow as a sub-workflow.
name, workflow, with. The sub-workflow’s state bag is grafted into the parent — no explicit return needed.
Detection rules
Gump infers the step kind from the fields present. Some combinations are invalid:agent+steps→ error (an agent step can’t have child steps)agent+workflow(without foreach) → errorworkflow+steps(without foreach) → errorguardon a non-agent step → error (guards monitor agents, not gates)withwithoutworkflow→ error