Hey @fisforfaheem regarding the “monopoly” point, that’s not the case. We’re not trying to push anyone to Composer with a specific model setup. Every Kimi release is evaluated, and whether we ship it as a separate model depends on the results. Kimi K2 and K2.5 are already available in the picker as built-in models, and newer versions including 2.7 can be used right now via a custom OpenAI-compatible endpoint or via OpenRouter: Bring your own API key | Cursor Docs
There’s no decision yet on making 2.7 first-party, and I can’t share an ETA.
@liquefy on BYOK, noted. We’re aware of some rough edges in the integration, and we’ve reported part of them already, for example Kimi/kimi-k2.5 cannot be called to execute tool calls in cursor and Requests are sent to incorrect endpoint when using base URL override. I can’t give a specific timeline for improvements, but I’ll pass the feedback along. If you hit a specific BYOK issue, please start a separate thread with details like the model, provider, and Request ID, that’ll help us debug it faster.