But then somebody commented on the post and I realized I would much rather see a new composer version with the new kimi version as its base model rather than the kimi model itself.
I must say composer is better in terms of quality, speed and price since it is separate of the API usage.
However there is not much information about how long it takes to produce a new composer model, if cursor team is interested in refreshing it this soon. Is there any way to get insight into this?
For example how long does it take approx. to make it? (I am out of my API usage now )
I would love knowing cursor team is working on new version with a new base model. It would be great to know what model is used as the composer base as well.
Quick clarification on the technical side: Composer 2 is Cursor’s own agentic model, not a wrapper on top of Kimi or another open source model. The docs say this clearly: “Cursor’s own agentic model designed to achieve frontier-level coding performance” Composer 2 | Cursor Docs. So a “new version of Composer based on Kimi K2.6” won’t happen in that form, since Composer is developed as its own separate line.
As for timelines and details of the next Composer iterations, we don’t announce anything publicly ahead of time. Everything that ships shows up here: Changelog · Cursor. If you’re interested, the best thing is to keep an eye on that page.
)