Has anyone else noticed that Composer 2.5 has become much worse recently?
I’ve been using it for a while and the difference is pretty obvious. Tasks that it used to handle quite well are now often handled in a really stupid way — losing context, making obvious mistakes, going in the wrong direction, or simply failing to finish the task.
Honestly, it feels like I’m using a much dumber version of Composer 2.5 than I was before.
I’m wondering if Cursor has recently changed something behind the scenes — reduced reasoning/compute, changed routing, context limits, etc.
If there was a change, I’d really like Cursor to be transparent about it.
Hey, thanks for the feedback. I get it, it feels bad when it seems like the model went off the rails.
On your question, if you explicitly select Composer 2.5, you are using Composer 2.5. We don’t swap your selected model to something cheaper in the background. If you use Auto, routing between models does happen by design. You can force Composer 2.5 in the model selector to remove that variable.
Quality can still vary from task to task. It depends on the context, repo size, and how the prompt is phrased. But if you’re seeing consistent degradation on the same kind of tasks that used to work fine, that’s worth looking at more closely.
To check if anything real is happening on our side, please send:
1 to 2 Request IDs from problematic requests right-click the chat top-right corner > Copy Request ID note that in Privacy Mode, Request ID availability is limited
a short description of the task that used to be fine but isn’t now
your Cursor version Help > About
With that, I can pass concrete details to the team to investigate. Let me know.
Yeah, feeling same. Forcing to grok 4.6 for sure to improve Elon Mask model.
You can see this force even in UI, by taking away model choice by the default, placing efficiency choice on the “type” section. I mean, who is really switching efficiencies?! lmfao
God bless cursor app doesnt force updates, so i still have old UI
So yeah, grok is a prio. Not bad model tho, relatively cheap.
Many developers in my organization feel the same. Composer 2.5 quality has degraded a lot since around 2 week ago. It is much dumber this week. It constantly ignore rules and skills.
@KhanhDo, “constantly ignores rules and skills” is something we can check in a concrete way. To see if there’s something real happening on our side, and not just differences from request to request, I need:
1 to 2 Request IDs from requests where this happened right top corner of the chat > Copy Request ID. Note that in Privacy Mode, Request ID availability is limited
A short example of what rule or skill was ignored and what you expected
Your Cursor version Help > About
Whether you’re using Composer 2.5 explicitly from the selector, or via Auto
With that, I can pass specific details to the team to investigate. With only a general feeling like “it got dumber,” we can’t reproduce it on our side.
@lenster, quick fact check. If you explicitly selected Composer 2.5 in the selector, you’re using Composer 2.5. There’s no background swap to a different model. Routing between models only happens in Auto mode, and that’s by design, not a hidden push to a specific model. So forcing Composer 2.5 in the selector removes that variable.
Send the Request IDs and I can move forward with your cases.
Yeah, im selecting specificly composer 2.5 time to time, but now mostly sitting only on grok 4.6, and using composer as a sub agent only.
I’m good tho, thanks for an offer, i will keep in mind that. If i will have any problem i would remember that i can get help here, thanks.
Hi, Dean! I’m actually also really worried about the fate of Composer 2.5 — it’s very important to me. Unfortunately, I can’t fully switch to Grok because it’s significantly more expensive after the discounts run out.
I recently saw in the news that Elon Musk bought Cursor. And that the OpenAI models will be removed soon. I’m willing to accept this, but I’m worried about the possible fate of Composer 2.5, as well as the prospect of Composer 3.0 being released. Unfortunately, there’s no other model that’s as effective and affordable. Do you have any information on this matter?
@lenster, no problem, the door’s open. If anything comes up, come back with a Request ID and I’ll jump in on that specific case.
One quick clarification so this doesn’t stay vague: if you explicitly pick Composer 2.5 in the selector, you’re using Composer 2.5. There’s no background switch to another model. Routing between models only happens in Auto mode, and that’s by design, not a hidden push to a specific model. So pinning Composer 2.5 in the selector removes that variable.
@KhanhDo, my offer from the post above still stands. To check if there’s anything real on our side (and not just request to request differences), please send:
1 to 2 Request IDs from problematic requests (top right of the chat > Copy Request ID. In Privacy Mode, Request ID availability is limited)
a short example of a rule or skill that got ignored, and what you expected
your Cursor version (Help > About)
whether you’re using Composer 2.5 explicitly from the selector or via Auto
With that info, I can pass concrete details to the team to investigate. With only a general feeling like it got worse, we won’t be able to reproduce it on our side.
Composer 2.5 is Cursor’s own model, and it’s not affected by OpenAI’s decision. It’s fully available and supported. If you explicitly select it in the model picker, you’re using it, and there’s no background swapping.
For OpenAI models (GPT), you’re right. Here’s the official reply from my colleague Colin in this thread:
So we’ll keep providing access to models in Cursor, and we’ll share updates on the details around OpenAI models over the next few weeks. For discussion and news, it’s best to follow the thread above.
As for future releases and model plans, I can’t share anything ahead of time since we don’t publish a roadmap. Please rely on the changelog What's New in Cursor — Latest Updates & Release Notes and official announcements, not third-party retellings.
If you notice a specific regression in Composer 2.5, send me 1 to 2 Request IDs with a short description of the task and I’ll pass it to the team.
Thank you for the detailed response! I’m just hoping that, due to the close integration with XAI Composer 2.5, it won’t be abandoned or replaced in favor of Grok until a direct, more advanced alternative is released at the same price, since this is an important model for many users, and it would be a shame to lose it without getting a better alternative.
