Check whether routing beats the default
Do this before you move a project's routing mode up to Auto, or when you wonder whether routing is worth its experiment budget. The Agents tab compares the work that ran on the router's pick with the work that ran on the project's default agent: how much of it merged and stayed, and what each success cost.
Who can do this: your organization's Owners and Admins, with intelligent routing on your plan. Without it, the Agents tab shows no routing results.
- In the sidebar, select Reports. The command center opens.
- To look at one project only, pick it under Project in the bar at the top. Leave it on All for your whole organization.
- Select the Agents tab and scroll past the agents to the routing results. They start with a Period filter.
- Pick a Period: Last 30 days, which it starts on, Last 7 days or Last 90 days. This period is its own: the range in the page's bar does not change it.
- Read the first card, headed All projects or the project's name:
- Dispatches: the tasks routing handled in the period.
- Router agreed: how often what ran was the router's own pick, such as 80% (4 of 5).
- Exploration: the share of tasks spent trying other runners. When the project has an experiment budget, it reads against it, such as 20% of 25% budget.
- Recommend: on projects in Recommend mode, how many suggestions people accepted, overridden or left with no response.
- Read Router pick vs default. Each group names what it Ran on, its Dispatches, its Survival (the share of its work that merged and stayed) and its Cost per success. A survival figure such as 80% (49–94%) · n=10 carries its range and how many outcomes it rests on: when the two groups' ranges overlap, the gap may be chance.
- If the card reads Survival and cost per success: No outcomes yet, no finished work from either group has been judged. Pick a longer Period, or come back once more of it has merged. No success yet means outcomes are in but none was a success.
- Read By project for one row per project: Dispatches, Router agreed, Accepted, Overridden, No response, Exploration, Router / default (tasks on each), Ran on (each runner and its count) and both groups' Survival and Cost per success, router first. A period with no routed tasks reads No dispatches in the last 30 days., with the period's own number of days.
- Act on it:
- The router pick survives as well or better, for less per success: move the project to Auto, as in Set a project's routing mode.
- People override most suggestions, or the router pick does worse: keep the project on Recommend, or narrow what routing may pick, as in Limit what intelligent routing can pick.
If the results don't load, the panel reads Routing unavailable; select Retry.
Related
- Compare agents and models by outcome: the same outcomes per agent, model or configuration.
- Choose what a task runs on: what routing chose for one task.
- Read the command center: the rest of the Agents tab.