logoalt Hacker News

ai-xyesterday at 6:02 PM5 repliesview on HN

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


Replies

johnfnyesterday at 6:24 PM

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.

show 4 replies
jedimasterttoday at 11:01 AM

> Model Routing will always be done better by models themselves.

> The models themselves will get better at this and frontier companies will simply give that capability

I would never trust something like model routing to the same company that would profit from it, and that goes for telling models doing their own routing when that could easily be trained into the model to make things more expensive. Sort of a conflict of interest.

Models are first and foremost trained by corporations.

show 1 reply
vanuatuyesterday at 6:48 PM

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.

CuriouslyCyesterday at 6:46 PM

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.

fnytoday at 12:48 AM

This is actually simpler to implement. You can have a AGENTS.md describing who is boot at what and then you have the agents converse over tmux.