Workflow Modules
The Model Router picks an Agent's model and prompt for every run. Change it on one screen, no release. Every choice is recorded with its reason.
How it works
An alias is a row an operator edits on the admin screen, and the next run picks up the change with no deploy. A single run can also override its own selection without touching the standing alias for everyone else.
Model lookup
No Agent carries a model name inside it. Each one asks the Model Router at run time and gets an answer back, or a safe default if nothing has been set yet. One lookup covers every Agent and every Module that uses a model.
Model alias
Edit the alias on the admin screen and the next run picks it up, with no deploy. The prompt resolves alongside the model, so it comes back as one answer.
Router monitoring
A single run can name its own selection without touching the standing alias. If that selection isn’t available, the call fails over automatically and the run keeps going. The failover is recorded, and everyone else’s alias stays as it was.
Budget guard
A budget guard checks spend at the moment the selection is made. Go over the line and the run continues on a cheaper selection instead of stopping. Every downgrade is written down with the run it affected.
Routing diagnostics
Each selection writes a machine-readable reason alongside it, so a past run traces back to what it used and why. An alias, an override, a failover and a budget downgrade each read differently in diagnostics, so you always know which one fired.
Per-Agent alias
The Model Router selects by the alias set for that Agent. It doesn’t read a request and decide the work needs a bigger model. Different behaviour only comes from setting a different alias.
A single run can name its own model without touching the standing alias. If that choice is not available, the call fails over and keeps going, and the switch gets written down.
A budget guard checks spend the moment a model gets picked. Go over the line and the run continues on a cheaper model instead of stopping, and the reason is recorded alongside it.
No. It selects by the alias an operator set for that Agent, and does not route by task complexity.
An operator edits the Agent’s alias on the admin screen. The next run uses it, with no deploy and no change inside the Agent.
The call fails over and the run finishes. The switch is recorded with the run, so it is visible afterwards.
Yes. Every selection records a machine-readable reason alongside the run, readable in diagnostics without reconstructing anything.
30 minutes on your Agents and how the Model Router records and traces each choice.
We use cookies to understand how the site is used and to connect form submissions to earlier visits. No analytics or marketing cookies are set until you choose. Privacy Policy