Ask a person, wait, then branch on the answer
Some steps need a person. The agent should not decide alone whether a refund is fair, or whether a change can ship. Rein lets a flow send the agent a request and wait for a typed answer.
The run stops at the request. The agent asks the person, then the flow starts again with the answer. No state is kept between runs, so the flow restarts with the answer it gets.
The answer is typed, like any other input. A yes or no answer branches the flow. A choice among fixed options branches it again, and every option has its own case.
This keeps the person in control of the decision, and the agent in control of the steps around it.
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.
- Pick the right model for each delegated taskDelegate each task to a subagent, with the model that fits it.