Flows

A flow is a graph of steps that runs in a known order: tool steps run your code, agent steps ask a model for a judgment, and edges between them decide what runs next. A flow is data, versioned and checked when it loads; every run of it is recorded step by step in its journal.

Use a flow when you know the order of the work (look up, decide, then act). Use a single agent when the model should decide the order.

• Write a flow: tool and agent steps, edges, and running it.
• Pass data between steps: a step's input from the run input and earlier steps, and the run's output.
• Branch a flow: edges that fire only when a condition holds.
• Join branches: a step that waits for whichever branches ran.
• Repeat steps in a loop: once per element of a list, or until a condition holds.
• Run steps in parallel: several tools on the same input at once.
• Retry a failing step: retries with backoff, and a time limit per step.
• Wait for an approval: a flow that stops until a person decides.
• Dry-run a flow: run the steps that only read, and stop before the first one that writes.

The examples build up one pack, acme, from the sample template (kindgi init acme --template=sample, or --template=python). Each page shows the tools it adds; Write a flow has the first ones. Where a model matters, the output is from Claude Haiku 4.5, registered with kindgi providers register --preset=anthropic (see Models).