lets do this organized and keep the bug reports + solutions as separate threads.
Each of those will have more information and we can share it with others having the same issue. Tag me if you have a thread with solutions and the cursor team if there are issues not yet resolved.
I will create a meta thread with common issues to post there the different cases with solutions as reference for anyone looking, and point others to the actual solutions. Primarily we should focus on v0.50 as others are not updated anymore. I will spread solutions where possible and sure @jdubb75 as well as other forum members can help.
@jdubb75 could you make a post about the intellicode/intelligence issue with details (version,…) so it can be tried by others? For now as I don’t have that issue I cant reproduce it.
I’ve decided not to renew my Cursor subscription. A while back, there were persistent issues with Gemini failing to edit files, and although I patiently tried to find solutions, the problems persisted with little improvement - file editing failures still occurred frequently.
In recent days, both the Gemini and Claude models have become completely unresponsive to slow requests. I tried various methods but got no response at all. I even waited 40 minutes just to see how long these requests would actually take, but ultimately gave up as it became clear the service was essentially unusable. I’ve now resorted to looking for alternative products.
I do have a pro subscription but the requests even in the default one are waaaaay slow. Sometimes it takes a few minutes, about 2-3 to resolve. If this isn’t fixed soon I’m gonna switch ides. Honestly, what’s this about?
to those experiencing slow responses/no response after limits: this came after students massively joined, Cursor is probably being hammered by requests and needs time to upgrade resources
to @danperks: I think a nice feature would be to make a ticketing system for bug reports and feedback, thus separating individual issues from a broader discussion of Cursor and AI, as of now its a chaotic mix and doesn’t allow to grow a niche of enthusiast, an added bonus is that a ticketing system will keep competitors out from leveraging this data to improve their products and promotes a direct, faster, responses to users that now seem ‘lost’ in this chaotic mix
I selected this as the solution, however, there are still a lot of major issues to address. Beyond smaller bugs people experience.
Someone mentioned the recent request slowdown is probably from students being given subs or discounts. I agree that this was a terrible decision and honestly was prone to people fraudulently abusing that offer. Hindsight is 20/20 but that should’ve been seen from kilometers away and restricted to only US or specified .edu emails.. very transparently to reduce the amount of issues coming in. Also basically destroyed the queue or however the slow requests work for pro users now it seems like - if that is the cause for recent performance issues.
Yeah, as long as the forum doesnt handle such things automatically there should be one central thread (or category at least) for the current version. With bugfixes so people dont start making tons of new bug reports
Hard not to considering it is pretty likely that all the student requests has now degraded paying users experience AND student experience on the product.
To add to your point, we should also definitely have a pinned post about new model releases as well. The forum is swarmed with Claude 4 posts, and if we had a pinned post to highlight issues, fixes, and updates from community devs as things progress it would already have significantly reduced the amount of clutter. Clutter that prevents other users from sifting through the forums in a more organized and convenient manner.
Not sure why these things still are not being implemented. Maybe leaders AND regulars need the ability to pin posts or to be able to request for them to be pinned by leaders.. Since you’re a regular @condor and seem to be highly active as well… >.>
It would probably be best to have the pinned posts in a section on the top posts page just above them so they’re VERY hard to miss for new comers or people just visiting.
@danperks@deanrie uhh idk who else I should tag @ericzakariasson ? lol. dont want to hit the whole admin/mod list. I’ll flag this post
No worries, yeah I agree, and the Cursor team is also informed. Its good also to see you active in many threads and with good conversations. Its well visible how its sometimes hard to get details to exclude causes or confirm solutions. This is crunch #1.
Cursor already planned improvements for the forum. Most likely they are so busy with core business stuff and especially with Claude 4 launch yesterday + AMA at same time ;), but it was great.
However the forum does take up their time and makes support harder (not just for us). I’m open to brainstorm or try things out.
One thing is clear: reply snippet for incomplete bug report should be short and personal, users dont fill in when its comprehensive.
I don’t know, but for me looks like Cursor getting worse and worse. It started with unable to do changes, then dropping connections and now it takes 10 minutes for requests. First time I see some system that is degrading so quickly. Im even thinking to disable updates or to go with other software.
Hi all, while we are working to improve on all the issues mentioned here, we’re still working to track down the causes of any slow performance.
It is a small minority who are seeing these issues with v0.50 and this therefore makes the issues hard to find and fix!
To clarify, there are two reasons you may have slow requests:
You have consumed all of your request allowance (usually 500 requests), and have used a significant volume of slow requests to the point where your requests are severely throttled
There is a technical bug or issue causing your requests to fail, error or just sit generating forever.
For the latter, please feel free to post a new bug report, with screenshots and request IDs to help us track down and fix these for you! Please @ me in these and we will try to get to them as soon as we can.
Regarding the suspicious activity issue, this is only in place for free tier users now and we have already decreased the sensitivity to ensure people are not incorrectly flagged by this system.
