Cursor Composer

“We seek to make all repetitive tasks be effectively done by cursor composer model which is the cheapest.”

“they were good for simpler coding tasks, but after the company purchase, they will probably end up merged with Grok”

“I was using Cursor's Composer quite a lot, even over frontier models, just because of how darn fast it was.”

“it's apparently quite token efficient, so why would it be impossible for a Chinese lab to achieve something similar?”

“Incredibly token efficient, fast, and gets the same quality as if you worked the whole thing with Fable/Opus/GPT”

“Composer hands me a quickly put together college project that was started the night before it was due.”

“I find it really hard to justify the other models for the performance/cost I'm getting with Composer 2.5.”

“Composer did a competent but not amazing job with a good plan. What I really liked though is it was fast”

“When you normalise for time and money, Composer 2.5 is way, way, way, way better than anything else out there.”

“ended up progressing with the composer code because it was easier to progress with improvements due to its faster response time”

“It's pretty good! It's not near frontier level insight generating genius, but it's regarded as very capable and trustable”

“which was decent but still a step back from GPT 5.5 and Opus 4.8. Though it's really good at UI.”

“Composer 2.5 worked just as well for me as opus 4.6, and was faster and actually worked better for quick bugfixes”

“It's night and day difference. You don't even have time to get distracted, you stay in the zone.”

“It is pretty bad. Just like with Composer 2, it's fast, but quality is nowhere near what Cursor claims with their benchmarks.”

“Just like with Composer 2, it's fast, but quality is nowhere near what Cursor claims with their benchmarks.”

“Seems like a promising and useful model but its probably scary how much customer data they fed into it”

“It's a model that runs inexpensively in their coding workflow that is creating results similar to opus or gpt.”

“they did the same for composer 2 which was evaled in close competition with frontier models, spoiler alert, it wasn’t even close in practice”

“they set themselves up for flack when they use whatever these evals are”

“it is surprisingly lacking in the actual coding department once you go for edits that need changes in multiple files”

“Composer is clearly dumber than the rest but then I only ask it dumb questions and it answers them really quickly.”

“I actually really like Composer 2. For my use case, between the planning tool, and getting it to ask a lot of clarifying questions, I regularly get very good results.”

“Conductor/Composer/Superset etc realized making the sidebar PRs/worktree focused rather than chat focused can feel great.”

“Seriously, this seems like cool work and enjoyed the post. But my basic trust in them has completely tanked.”

“Acceptable in backend coding, not quite good enough in frontend coding, and quite weak at generating texts like PR descriptions or commit messages.”

“Cursor's research team is highly respected within the industry, and what they've done is quite impressive.”

“it works okay (yet to be tested whether it is actually smarter than Opus 4.6), but it is not bad at all”

“That doesn't appear to be the case here (Kimi's license requires publicly acknowledging Kimi is used for anyone operating at Cursor's scale).”

“If Composer is benchmarking better than Opus and costs $0.08 per request that's a win for everyone.”

“it's so damn fast that I can iterate on the result a few times before Opus would have finished”

“The speed and cost effectiveness are just hard to beat.”

“Cursor Composer is a lot faster and really nice for some tasks that don't require lots of context”

“This blog post doesn't really give any reason to use it besides "it's better on Cursor's internal benchmark"”

“just lightning fast compared to the others...but sometimes don't find the solution if it's too complicated”

“I can even use "cheap" models like their Composer-1 and get great results in the planning phase”

“composer 1 is great at following plan instructions so after some careful time providing the right context and building a plan, it basically never messes up the implementation”

“It's about the same quality of code output of the aforementioned models but about 4x as fast.”

“not tuned to be that agentic, so it's better for one-shot code changes than long-running tasks”

“It enables a totally different way of AI coding - instead of giving the LLM a long prompt and waiting minutes for it to finish, you give it a shorter prompt to just write one small thing and it finishes in seconds.”