Are you concerned about security issues, I think the kimi code extension is still in technical preview?
Also does it allow the agent swarm feature?
Are you concerned about security issues, I think the kimi code extension is still in technical preview?
Also does it allow the agent swarm feature?
I canāt imagine how this would work for regular development. Imagine the merge conflicts if 100 devs work on the same app.
What are they waiting for to implement the model natively?
Theyāre waiting for Trumpās sovereign approval at the national level.
Honestly am surprised it has not been added yet. as far as i know, this model is genuinely fun and good to use
I got the KimiK2.5 running on CURSOR using the āoverride Open ai urlā feature.
The inference url: https://api.fireworks.ai/inference/v1 Fireworks is blazingly fast, but you will soon hit rate limits.
Bruh they integrated Opus 4.6 right away. Weāre still left waiting for Kimi K2.5
@Colin when can we expect integration? Whatās up with the holdup?
빨리 ģ¶ź°ķ“주ģøģ
Kimi K2.5 is absurdly cheap. If users realize a near-free model handles most coding tasks, the justification for $60ā$200/month tiers falls apart. Those tiers exist because serving expensive models like Opus costs real money. Iād happily keep paying $20/month and use K2.5, thatās actually more margin for Cursor. But the risk for them is that users stop upgrading. Classic cannibalization dilemma. Would love transparency from the Cursor team on whether this is on the roadmap.
Thatās spot on analysis. I think what they should do instead is just promote agent swarms if they still wanna justify value for power users, so users still can burn tokens and demand for highter tiers, rather than artificially limit access to models
I donāt think they can charge whatever they want, because open-source software will provide better and cheaper alternatives once it has caught up. Cursor is obviously playing the money game, but not for long.
I have seen some videos and benchmarks of Kimi K2.5. I would love to try this little guy in Cursor and see if it can solve token cost problems.
@deanrie please add this.
But does that really matter? With long running agents, bugbot, and multiple runners, users will use the credits ādoing moreā
Another point to consider is: $200 users often consume $600 in tokens. Whilst many $20/60 users on Kimi could end up only using a fraction of their allowance
I think we are more likely to see a tuned Kimi as a Composer model, maybe we will get the base at the same time. Very high TPS for x2-3 the price, which will pull users away from the base model
composer 1.5 out with price 3.5 input and 17.5 output, I donāt think we will see kimi 2.5 soon.
Still waiting on Kimi K2.5, while Opus 4.6 was added instantly.
Iāve seen a few sources that are saying thereās some issues with Kimiās API that make tool calling crash and most likely problematic in the context of Cursor.
I would at least appreciate some of transparency from Cursor on exactly why K2.5 has not been added.
It certainly feels like Cursor does not want to add these token efficient models to prevent cannibalization of higher plans. While Iām not sure if this is true, transparency from Cursor would easily resolve this speculation.
Even just a response to this thread would be better than nothing!
this is an old model, not the new K2.5
Ah, why is the price not listed for K2.0 though..