Every single update should have at least 1 or 2 lines of notes somewhere that we can read to know what to expect. You can keep it somewhere separate from the changelog page. Even if it’s minor bug fixes. I know you keep the changelog page for the major things. But the moment you push and update we need to know or have some idea of what’s coming. So that when there is an issue we can report properly. We need to know.
Facts. 100% agree. Especially at a time like this. Don’t get me wrong, I am neutral if not positive on Grok and related. But when Cursor is constantly adjusting quotas, changing terms, having friction (you know who), and then they push out Grok Bots (pretty beta still), everything just feels like a black box mystery. It is frustrating and directionless for customers who have paid real money for their service.
As I’ve seen some members have said before, “a lot of things are not controlled by staff in this forum anyway.” I’d agree. I feel for them. I am thankful and amazed for their hard work by all means. Nonetheless, I would suggest that a properly managed and well-implemented changelog would have also made their life easier. A lot of questions and problems arise because of bad communication (i.e. bad changelog and everything OP mentioned).
I am hopeful for Cursor, still. But the DevOps pipeline would need some DevOps, frankly.