Seconding this, it would be really, really nice to get some more information when functionality is added or when core functionality undergoes significant changes between versions.
It feels like we often see huge reversals in how functionality works between one build and the next, or sweet new features being added that are really vaguely defined, with the change log only briefly mentioned these changes if at all.
The biggest example for me was with copilot++ switching from being tied to a key to running automatically, which wasn’t documented for months. The shift between “we usually run this and github copilot at the same time” to “it overrides github copilot” was never really explained as far as I can tell.
I understand that documenting these changes and keeping the existing documentation up to date can be a tedious part of the development process, especially when building at such a fast pace as Cursor has been.
However, I would greatly appreciate more attention being given to a) documenting these changes and b) ensuring that the existing documentation remains current.
The gif suggestion is a great one and would go a long way to helping out - especially if they’re included in the change notes. For a bit of inspiration here, The Browser Company / Arc are shipping amazing new things every week, and do an incredible job of sharing their release notes: a mini overview with pics and gifs, gifs via twitter, quick round up vids, and text release notes.
It’s hard with a small team, but when you’re shipping fast it’s more important than ever to bring us along for the ride.