have been thinking a bunch about model routing and related things current thoughts here, would love feedback: 1/ there is a difference betwe…

have been thinking a bunch about model routing and related things current thoughts here, would love feedback: 1/ there is a difference between "model routing" and "model council" "model routing" = route to one best model. i think only real reason to do this is cost "model council" = pass to many models at the same time, then aggregate responses. this is done to push frontier performance 2/ "model council" seems to be having a moment recent. @OpenRouter did their Fusion thing, @SakanaAILabs did fugu I do think there are use cases where this can be useful - @nlarusstone highlights how they use it for tough bio problems and the most recent "max agency" i'm unsure how you would use it to drive a main agent, but as a "tool" makes sense. similar to how anthropic's advisor tool 3/ model routing in theory sounds nice and im probably a bit more bullish that dax. I dont think expecting ALL users to be on top of which model to use when is feasible. (maybe for coding its more feasible, im thinking broader tho). prompt caching is a real concern. maybe you can heavily bias towards not switching once its been routed once initially? 4/ main reason for model routing is cost. but there are probably other (simpler) levers to pull first. eg putting spending caps, maybe on a per model basis (you get X dollars for opus, then need to use sonnet) at langchain we are doing (4) first (basic cost controls/policies: https://www.langchain.com/blog/how-we-made-coding-agent-spend-predictable) but considering routing and other options i have low conviction on model routers - very open to changing my mind but this is a snapshot of my current thoughts - i don't think it's good to not be aware of what model you're using. coding with LLMs is a skill you develop and getting a feel for models is part of that - peopl…

Source: Harrison Chase (X) | 2026-06-22