Docs

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
  • Navigation: LLM Cost Metrics in the sidebar, then LLM routing control under All tools, in the Budget and routing group

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. Click a tier button to change it; the edit is highlighted and the repo shows unsaved changes before you open the PR.
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 is a config-only change to one file, and the body shows each surface with its prior tier and the model change, so undo is a single revert PR that restores exactly what you see.

Configure

The tracked repo needs a .claude/brain/llm-routing.json 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.

Read more

Last updated