Why not https://models.dev?

[akaytatsu]

Currently, the listing of available models for Crush is a separate repository maintained by the team itself.

I’d like to bring a discussion here: why do I use Crush, or some terminal-based AI agent? Because it gives me the freedom to choose what I want to use — which model to use.

I think Crush is amazing, but when it comes to choosing which model to use, I still feel like I don’t have a choice. I’m forced to pick a model that the Crush team selected first. The model I have to use was preselected by the Crush team. This takes away my freedom of choice.

The https://models.dev platform gives much greater freedom — practically any model in existence, across many different providers. For example, as soon as GLM4.5 was released, about 2 hours later it was already available on https://models.dev, across multiple different providers.

I do have GLM 4.5 on Crush, but for example, I don’t have the free trial versions available on OpenRouter. And why is that?

Right now, it’s becoming natural and organic for terminal tools to use https://models.dev as the repository for LLM discovery.

It would certainly be a big step forward — a huge leap in freedom — to migrate to https://models.dev.

[caarlos0]

I think @kujtimiihoxha can better answer this one...

[LarsArtmann]

@kujtimiihoxha can you provide us with a quick reply over here?

[kujtimiihoxha]

Sure, we have a different set of configurations we track and use in crush, we also plan to add some other crush specific configurations to our models in catwalk.