Hey, I get that waiting this long with no progress is frustrating, especially when the request looks obvious.
On the accusation, I want to be clear: there’s no intentional stalling here, and we’re not trying to lock anyone into the Cursor API. BYOK via Override OpenAI Base URL is an officially supported setup, and we’re not removing it. The reason there hasn’t been progress is simpler and less conspiratorial: per-model and per-provider routing affects how model selection and routing work overall, and that area hasn’t been in active development yet. I still don’t have an ETA, and I won’t make one up.
We’re tracking the request and it’s still on our radar. When we have something concrete, I’ll reply here.
For now, the workaround is the same: turn off Override OpenAI Base URL when you need models from your Cursor subscription, then turn it back on for your own endpoint. I know that’s inconvenient.
One more thing: if your case is specifically about routing, where Cursor-managed models get sent to your custom endpoint, not about a separate base URL per model, that’s being handled in a separate thread: Cursor-managed models are routed through Override OpenAI Base URL. Please share routing details there so we don’t mix it up with the feature request.