4 ms·
Cursor's composer models are finetuned kimi
by schmorptron 4mo ago
Cursor's composer models are finetuned kimi
- varispeed 4mo agoThey are unusable (unless you want to deliberately destroy your codebase). So if Cursor's models are Kimi based, then well. I'll skip them altogether.
- bel8 4mo agoI wouldn't skip at least testing the original. Model distilling done by Cursor could be the culprit.
- Bnjoroge 4mo agoThey are far from unusable. They aork great for 80-90% of a typical full stack dev. Alot less useful for more noche stuff
- qingcharles 4mo agoThey're not unusable, they're just bad when compared with all the real frontier models.
- vidarh 4mo agoKimi works great in their CLI, but their CLI has a number of workarounds for quirks of their models, including detecting when the model gets into a loop, and reverting to a checkpoint but letting the model compose a "message" to its past self (search their CLI for "BackToTheFuture"...) It doesn't work so well in a harness that doesn't take those quirks into account.
- jmcqk6 4mo agoI'm using Composer extensively, and it works great for me. Your experiences are not universal.
- esskay 4mo agoComposer 1.x was poor. The new one is a totally different beast and absolutely fine for day to day.
- ok_dad 4mo agoI only use composer 2.5 day to day and it works fine with human review.
- AgentMasterRace 4mo agoComposer is really good, but just like any Chinese model it needs a good plan. It's cheap and fast, in 1 month of pro I used the equivalent of 500$ in API credit for it.