Pick the right model for each delegated task
Not every task needs the largest model. A simple lookup can go to a smaller model. A hard design question may need the largest one. Choosing the model is a decision, so Rein writes it as a flow.
The first question asks whether the task is simple. A simple task goes to a subagent with a smaller model. Other tasks ask one more question about how much reasoning they need.
Delegation uses a template. A template is text with slots, such as the model and the task. The flow fills the slots, and the agent sends the result to a subagent.
Each model choice has a case. Add a new option, and the checker reports every place that still needs a case.
The flow in one picture
Alpha, private
Try this with early access
Rein is a proof of concept. Syntax and tools can still change. Request early access by email, and tell us which decision flow you want to build.
Related use cases
- Decide the next step for each pull requestDecide whether a pull request merges, gets a review, or waits for CI.
- Route each alert to one clear next stepRoute a production alert to a person, a runbook, or a ticket.
- Answer tickets, or hand them to a personAnswer a support ticket, start a refund, or hand it to a person.
- Ask a person, wait, then branch on the answerAsk a person a question, wait for the answer, then branch on it.