Skip to main content
By the end of this guide you have a workflow whose three agent steps run on three different models: a fast one for a quick read, a flagship that thinks hard for the step that has to be right, and one exact model for boilerplate. You also check which model answered each step. Every agent step takes its own model value, so routing is declared per step in the workflow file. The value names a tier or a model, and can carry the thinking level that step runs at.

Before you begin

1

Pick a model value for each step

A step’s model is one of these:thinking_level is low, medium, high, xhigh or max, and is lowered to the highest level the chosen model supports. Prefer tags to ids: a tier keeps working when you change providers, and an id fails when you have no provider for it.
2

Write the workflow

.reliant/workflows/model-per-step.yaml
The agents have no tools, so the run stays small. A real step keeps its tools and changes only model.
3

Check it locally

Add a scenario that mocks each step’s answer, then validate, lint and run it. None of this calls a model.
.reliant/workflows/model-per-step/scenarios/answers_flow_through.yaml
terminal
terminal
Validation checks the shape of each model value. Whether you have a provider for it is decided when the step runs.
4

Run it and see which model answered each step

terminal
terminal
reliant workflow status shows each step’s status and timing, not its model. Each saved reply records the model that produced it, after the tier was resolved. Read them with ChatService/ListMessages, one of the public API’s procedures, using an API token from reliant auth token create:
terminal
terminal
The replies come back in step order: fast resolved to Claude 4.5 Haiku, flagship to Claude 5.5 Opus, and the id ran as named. With other providers connected, the two tiers resolve to other models.
5

Let a preset or the person running it choose

A step can take its model from a preset instead. The built-in researcher preset brings a flagship model at low thinking, with its tools and skills. Values in args override the preset’s.To let whoever runs the workflow pick the model, declare a model input. merge() keeps their choice but pins one setting, the way Get It Right always runs its reviewer at high:
.reliant/workflows/model-per-step-input.yaml
In the app the input appears as a model picker. From the CLI, pass a model id with --input model=<model id>.

What this does not do

  • It doesn’t show the thinking level a step ran at. The reply records the model, but no message, status or event records the effort. The level is lowered to what the model supports, so the value you set is an upper bound.
  • It doesn’t fall back from an id to another model. A step that names a model you have no provider for fails. Use tags when the workflow should run for people with different providers.
  • It doesn’t change which tier a tag means. The models behind fast or flagship, and the effort each runs at, are set per machine in ~/.reliant/config.yaml (model configuration).

Next steps

Run a local LLM coding agent

Put one step on a model served on your own hardware.

Model configuration

Reorder a tier, change its thinking level, add custom models.

Presets

Bundle a model, tools and a prompt, and choose a provider when one is rate-limited.

How workflows run

What happens inside each agent step.