Kimi 2.7 support in Cursor

Ideas Feature Requests
, , ,
1

Feature request for product/service

AI Models

Describe the request

Kimi 2.7 has now been released by the Kimi/Moonshot team, while the previous Kimi K2.6 request still does not seem to have been addressed.

Could Cursor add support for Kimi 2.7? Kimi models have been strong for coding and agentic workflows, so having the latest version available in Cursor would be very useful for developers who want to use Kimi directly inside the editor.

Release announcement: Kimi.ai on X: "šŸŒ˜ Kimi-K2.7-Code, our latest coding model, is now released and open-sourced! šŸ”· Improved coding & agent performance over K2.6: +21.8% on Kimi Code Bench v2, +11.0% on Program Bench, and +31.5% on MLS Bench Lite. šŸ”· Reasoning efficiency: Less overthinking, with 30% lower https://t.co/jFS7I40avs" / X
Previous request: Kimi K2.6 Released - Request - #46 by Antti

Operating System (if it applies)

Windows 10/11

4

Hey, thanks for the feature request. We do see requests for newer Kimi versions, itā€™s a popular topic, and there are related threads here: Kimi K2.6 Released - Request and Add More Chinese LLMs?.

Status update, honestly: we donā€™t have a decision yet to add Kimi 2.7 as a first-party model, and I canā€™t share an ETA. The team reviews each Kimi release and decides based on the results whether to ship it as a separate model.

For now, there are two options:

  • Kimi K2 and Kimi K2.5 are already available as built-in models in the model picker.
  • Newer versions, including 2.7, can be used via a custom OpenAI-compatible endpoint or OpenRouter. In Cursor Settings, set the provider base URL and API key. Guide: Bring your own API key | Cursor Docs
5

Makes sense, I personally would not mind having fewer models supported by Cursor, but the BYOK system is borderline unusable. There are so many improvements it needs for seamless integration and people would be happy. Are there any plans to improve BYOK support?

6

why are we stuck with ā€œKimi K2.5ā€ why still not 2.7 code?? you guys are doing monopoly with composer

this is monopoly you guys are playing so people dont use it and use ur damn composerā€¦ we want kimi 2.7 urgently

8

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.

9

in regards to BYOK, I dontm ean a specific issue with some model and sorry for clogging this thread but it is kind of related. I mean more of an architectural overhaul, currently I can add one openai compatible url and sometimes it works, sometimes not. I would love the ability to add as many custom urls as I want with more options etc.

10

+1 kimi 2.7 needed