3 ms·
The best solution to this for me is to self host litellm or a different router and use model aliases. For example I have a model called "coding" and when a new
by geek_at 1mo ago
The best solution to this for me is to self host litellm or a different router and use model aliases. For example I have a model called "coding" and when a new good model comes out I just switch the backend without needing to change the alias or the key in my projects (opencode, etc).
I have a few of them even a smart router called "agents" which will use local models but if it thinks the request might require higher reasoning it's routing to a different model
- try-working 1mo agoI built a router that lets you route between local and cloud models. Link in my profile.
- embedding-shape 1mo agoYeah, I also built my own "router" for this: if (process.env.LOCAL_MODEL { http('localhost:3000/v1/completions')... } else { http('api.openrouter.ai/v1/completions')... }
- nvme0n1p1 1mo agoBrilliant! I'd like to invest $10M. Who should I make the check out to?