Model Routing will always be done better by models themselves. Plus routing loses context making it more expensive and less reliable.

Model Routing is just Bitter lesson. The models themselves will get better at this and frontier companies will simply give that capability

▲

johnfn 3 hours ago | parent | next [-]

This doesn’t seem obviously true, eg an Anthropic model will never route to Kimi even if it were best suited for a particular task.

▲

posix_compliant 3 hours ago | parent | next [-]

I think what the parent is saying is that the model itself has the best context for whether a portion of a request should be routed. The specifics of that routing (e.g., should you route to KimiK2) are something that can be trained, finetuned, or even included in a model's startup context.

▲

maCDzP 2 hours ago | parent | prev | next [-]

Has anyone tried that? I have a feeling that if I put it a prompt Claude would comply. But I am all in on the Claude cool aid.

	▲	johnfn 2 hours ago \| parent [-]
		Sure Claude would comply, but Anthropic has no financial (or other) incentive to optimize this, so there’s no reason to expect it to be particularly good. It would be like asking the clerk at a Whole Foods which grocery store in the city sells the cheapest eggs. He’d probably answer - he might not even say Whole Foods - but WF is hardly teaching all their staff the best methods to answer this question in training. (Heh, training.)

▲

siva7 3 hours ago | parent | prev | next [-]

Why should it? An Anthropic model is architecturally optimized for Anthropic models, routing it to Kimi makes zero sense

	▲	anon7000 2 hours ago \| parent \| next [-]
		Which is why 3rd party routers which do route between different models may have an edge. It means they can compete on cost, and it’s definitely not clear that the architectural optimization is always going to be higher quality or cheaper. It might be, but everything changes constantly, so locking into a single model family/company is very much not ideal
	▲	2 hours ago \| parent \| prev [-]
		[deleted]

▲

MagicMoonlight 37 minutes ago | parent | prev [-]

[dead]

▲

vanuatu 3 hours ago | parent | prev | next [-]

i think you're thinking of subagent routing

model routing in this case is cross-provider

Imo the main issue behind model routing is you need to figure out how much intelligence a new task takes, which is a very non trivial problem. Presumably, a organization knows this about their own tasks and is better suited to built in-house compared to outsourcing to a vendor.

▲

CuriouslyC 3 hours ago | parent | prev [-]

Model routing by the model itself requires the model to pull in a lot of context and it's likely more efficiently just done by people with the context already in their head, even assuming the model is perfect at routing (which last I checked, Claude definitely isn't). I wouldn't trust ML model routers.