Tab · Insights
LLM routing control
Cut spend without leaving the dashboard — edit a tier mapping, get a PR. Edit each repo's tier mappings and open a PR with the change. Control plane for the routing management agent.
See it in motion
Where to find it
- Localhost:
/llm-routing-control.html?repo=<id> - API:
POST /api/llm-routing/propose - Keyboard: ⌘ K then
routing - Sidebar: Insights → LLM routing control
What it does for you
Every surface, every tier, in one editable table.Each route in
llm-routing.json shows up as a row with its current tier. Change the dropdown; preview the diff before you commit.One click opens the PR against the tracked repo.The dashboard runs
gh pr create from a branch in the tracked repo with the routing change. CI runs the repo's own tests; you approve in the normal flow.Reverts are first-class.Every routing PR carries a rollback summary in the body — model, prior tier, observed spend delta — so undo is a single revert PR with the math already in it.
Configure
The tracked repo needs an llm-routing.json at its root and the GitHub CLI authenticated as a user with PR-create permission. The dashboard never pushes to main — it branches, opens, and lets your CI gate.
Use it well
Pair this tab with App LLM calls. The recommendation column there points at the change; this tab is where you apply it. Don't bulk-change tiers — one surface per PR keeps the rollback simple if a regression slips in.