I don’t know recently from 9th Sep the composer 2.5 performance completely dropped and hallucinating and not even able to read the repos or local folder files like earlier. why? are you killing cursor composer 2.5 to make user use grok 4.6 or it is really went bad all of a sudden? also I have noticed the recent cursor usage feels like I am using a cloud computer rather an app installed in my pc? why? does any one have any idea what’s happening with Cursor and composer 2.5?
I’m glad I’m not the only one who noticed this. At times, Composer 2.5 suddenly got really bad. It seems to be better again now, though. Is it the same for you, @Vishwanath_Studios ?
yes, it’s working fine now but when compared code execution before and now I still feel bit off about it. @Greenlentil
I suspect one possible reason is that the system prompts that Cursor uses internally now are all finetuned for Grok.
Hey all,
To be completely straightforward: there is no intentional nerfing of any models going on! We love Composer 2.5 and would take any quality degradation seriously.
If you’re experiencing issues with Composer 2.5, the most helpful thing you can share is a Request ID. It gives us what we need to investigate.
how to get the id you are asked?
@Vishwanath_Studios - At the top of your prompt window. Click the 3 dots → Copy → Copy Request ID. 
is it safe to share here? or do you provide me a mail id so that i can share the id. Also will you be able to read the contents in the chat or conversations?
Yes, Request IDs are safe to share publicly. What’s available for us to see depends on your privacy mode – read more here.