i dont mind you guys pushing daily updates at all. so far i got lucky and nothing bad happened. but maybe consider giving users a rollback option, if this is easily feasible – so users can jump back to their old version with the click of a button.
I have to agree. Those daily updates are irritating.
Please look over you release cycles and only deploy stable releases.
One hot fix occasionally is OK, but small fixes everyday is unprofessional and not acceptable. You will loose customers if keep doing like this.
Just canceled our Cursor subscription and advised my employer to do the same. I had previously reported Cursor Rules not working and, for some reason, the issue was closed without a resolution.
Before the latest update, I was at least able to provide rules to the context manually, but this is now broken, too. There is no longer any way for me to use Cursor Rules (though, I concede it does not affect everyone).
We are evaluating Claude Code, which is unfortunately much more expensive, but doesn’t seem to have issues with using encoded domain knowledge; the primary use case we had Rules setup for.
EDIT: I now realize they automatically close the issue after some time past the last reply, but for such an integral feature failure, I don’t think this is a good idea. Rules are just… not usable for me. I’ve seen enough people encounter this that I find unlikely that the Cursor team doesn’t know about it.
While I acknowledge that your team may not be seeing this report, there were many people on the original thread saying they were also encountering the issue. I expect some degree of them are likely just not saying anything since they assume they no longer work. I don’t have Cursor active any longer, but I am certain you could likely find others still hitting this issue based on the number of people who were responding to the previous report.
Thank you for your feedback. We already implemented improvements based on the previous thread. For any further improvements we would need a Request ID to see what goes wrong.
