Hello, Kimi K3 is here and looks interesting, would love to see it in Cursor!
It seems to have excellent performance in 3D game development.
ArtificialAnalysis:
Kimi Blog:
Links:
Feature request for product/service
AI Models
Describe the request
Hey everyone,
K3 just dropped today and the specs look incredibly promising. It’s ultra-lightweight, blazing fast, and brings a true local-first architecture to dev environments.
For Cursor users, native integration with K3 would be a huge deal: it means seamless local context, much faster runtimes, and a highly efficient workspace without hogging system resources.
Would love to see the team put K3 on the roadmap for integration.
If you want this too, please upvote so the team can get it on their radar.
A better outcome would be to conduct post training based on K3 and release composer3. If cursor does not have its own model support, its competitiveness will decrease
Agreed. It probably makes sense as a two-step approach. Short-term, just add basic K3 support so we can use it. Long-term, definitely leverage it for post-training to power Composer 3. From a user standpoint, Composer brings much higher value, so that’s what we really want to see.
We’ve been excited about a lot of recent open source models and added them to Cursor (Kimi K2.7, GLM 5.2)! We are looking at Kimi K3.
Totally agreed
100%
Hello, just a heads-up that we’ve had to switch to OpenCode in order to use K3. Would really love to switch back whenever you’ve added it to Cursor, as we’d obviously prefer not to have to switch in order to get the latest model.
I have a feeling that it is supposed for Composer to merge with Grok since Cursor got bought by SpaceX.
Not really the plan at the moment! Composer and Grok are two different weight classes of models, and we’re continuing to invest in the next version of Composer!
From our announcement of Grok 4.5:
Grok 4.5 and Composer 2.5 are two different model weight classes, and we’re excited to support both sizes and weights. Composer 2.5 will remain offered, and we will release new models of this size going forward.
Hey! Is there a blog post or some source where you go deeper on that distinction? I’ve seen composer 2.5 score pretty high on next.js benchmark, so this is my default for coding.
Do you plan to re-base Composer on Kimi 3? At least from the public benchmarks is way better than Grok 4.5 which makes Grok kind of lower weight class if you do that 
yeap, kimi k3 looks greate - we need this 
Chinese open weight models like Kimi K3 are similar quality to Fable but 1/3 cheaper. This creates large incentive to move to Chinese models for everything from API to vibe coding. I believe SpaceX which owns Cursor now can’t afford to allow users to use Chinese models. Personally, I’m not a fan of China, but hey, you can deploy it on your own servers with no access to funny business.
Can you tell me the reason why you don’t like China?
It would be cool if Cursor hosts Kimi K3 on SpaceX’s infrastructure and provides it as an API or even First-party model for us 
好主意
kimi wont release K3 weights until july 27, so there’s that.
and also next composer is trained from scratch as per info running around reddit, not based on k2.5 as composer 2.5 did
we are going to see more and more other providers of AI LLMs, and something tells me Cursor will not support them
have you heard the story of Xu Xiaodong?