>> it's definitely the best way to try out new models without fiddling with each providers distinct APIs which is becoming a recurring concern as of late
Why not... Cursor?
back
4 comments
Cursor only supports a single model (Kimi K2.5) not made by the Big 4 labs (OpenAI, Anthropic, Google, xAI). Cursor is actually extremely bad at wide model support.
OpenCode is much better at it.
And its own model (Composer 2.5)
Which is finetuned Kimi 2.5
Cursor is functionally "one of the big 4 labs" (SpaceX).
First, calling xAI one of the big labs is pretty funny.
Second, Cursor hasn’t been acquired by SpaceX yet, and there’s a good chance they never will be.
I use Cursor with OpenRouter for some projects and it's great. Most of the time I just use Auto and let Cursor use its model or choose. If I run out of quota, or I'm not getting what I want, I switch off Auto and use OpenRouter to pick Opus, Codex, or whoever(all are available). Can continue the same context if you want, type "please continue" in the agent prompt, and on you go.
Cursor has limits even when using your own key. I was even cut off using a local model. I guess they use some sort of harness that requires non-local resources? I'm not sure I've actually tried to use Cursor in a fully-offline scenario yet. Cline works well enough and doesn't require any sign-up.
Cursor's coverage on open weight models is very minimal, and it's irrelevant for testing models in your actual application.