I’m trialing Cursor and liking a lot of it. What worries me is that as basically a fork of VSCode, it should be almost right on time with offiical releases (or, as they keep writing in the forum, just a few weeks behind to make sure latest release is stable).
At the moment Cursor is stuck to 1.91.1, which is a release from June and we’re now at the end of September.
If I’m going to pay a monthly subscription, I’d like to see what’s the plan and the real commitment to stick to it. The beauty of VSCode is the very active development, and Cursor should have a rigid plan of following up any release after maybe 2 weeks and always stick to it.
We stay slightly behind the latest releases of VSCode for two reasons:
Especially with new features, there are often bug fixes that come to VSCode after an update to fix things, which we have chosen to wait for instead of trying to always be on the latest VSCode version
As things change in VSCode, it takes our engineer’s time to upgrade the VSCode version Cursor is based off, taking time away from working on other areas of Cursor.
If there is a major feature added to VSCode that people want, or an update to an extension that Cursor is unable to get, we have no problem prioritizing a VSCode update, but I would usually expect Cursor to be somewhat behind VSCode most of the time.
We are currently testing VSCode 1.96.2, which was released in November '24, for a future update, which should come to users a future update soon!
It’s one of the worst downside to Cursor at this point. Like now I’m using VS Code simply because of that. There is a lot of bugs right now with dev container and certain extensions. I’m not sure why, but ElixirLS keep crashing inside a dev container on Cursor.
Copilot have released their model selector as well (Sonnet 3.5, o1) since the last release. I would like the be able to use the composer and the chat with Copilot. Currently I can’t with Cursor because the version is too far behind.
So now I’m using VS Code inside the dev container and Cursor outside of the container. When I want to run a process or test I use VS Code, when I want to use the composer I use Cursor, VS Code for the chat (context is now larger on Copilot, 128k token). So I keep switching back and forth.
Dev containers have specifically been a bit of a pain point for Cursor in the past, but we’ve got some updates coming soon that should hopefully stabilise things there!