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!
Can we get the latest vscode version? since there are some settings that are quite good shipped in the latest. Also, can you make it to automatically update? I was seeing previous posts that people have to ask for the update. Seems kinda basic.
Hi it may seem basic but its its unfortunately not. Its not update vscode, copy files and done - simple process.
Cursor team has explained in the other posts you have likely seen, that there are changes that clash with Cursor functionality as MS integrates their own needs. They also must test those changes and it takes time per vscode version update. Also at same time users request other features as highest priority if they dont use newest vscode features.
Hope this has explained why its not basic.
The Cursor team is aware of users having requested upgrades to vscode version and several have been integrated and more will sure come.
I’m not sure about settings, but 1.19.4 supports pytest-describe and a number of other QoL improvements. Understood about the complexity, of course. Does Cursor have a policy or goal re: how up-to-date or how frequently it’s updated?
VSCode is now on 1.100, while Cursor is still 1.96.2 from last November.
Somewhat behind is reasonable but this is half a year.
Yes, much of the focus has been Copilot (which has cool stuff like native voice-chat), but there are plenty of other things + extensions requiring a higher minimum version etc.
A few examples (I’m sure others could make their own list):
Soft-delete in source control.
Floating window modes.
Semantic text search.
Streamable HTTP transport, image output, and progress messages for MCP.
I’m reaching out to inquire about the possibility of an upcoming VSCode version bump for Cursor.
Microsoft recently announced the TypeScript (Native Preview) extension, which is a port of the TypeScript compiler to Go. The performance improvements sound fantastic, with reports of up to 10x faster build times and significantly improved editor responsiveness.
I’m currently using Cursor which use VSCode version 1.96.2. It appears that the new TypeScript (Native Preview) extension is not compatible with this version of VSCode.
Given the potential benefits of this new TypeScript tooling for developer productivity, especially on large codebases, it would be great if Cursor could support it soon.
Could the Cursor team share if there are any plans to update the underlying VSCode version in an upcoming release to ensure compatibility with such new extensions?
hey love cursor and really want to use the native type checker for typescript lsp to be faster would love if we could upgrade the base code version to ^1.100.0. such that the new lsp extension could work
This seems unacceptable to me. Before anything AI, you have to build a great IDE. VSCode is already not the greatest IDE and far behind the polished product offerings from Jetbrains.
The minimum bar should be keeping up with the VSCode improvements.
I suggest putting this issue at the top of your roadmap. This is slowly becoming a deal breaker. Especially now that the TypeScript team released a preview version of their tsc-go port, that we cannot install due to the underlying vscode version. A 10 times performance improvement in the IDE is more important for us than a few AI features.
Our team has 14 licenses activated right now, and we are seriously considering switching back to VSCode due to this.
One thing that’s keeping me from using Cursor is the fact that it’s base VSCODE version excludes me from using the latest version of the ORACLE SQL-Developer for VSCODE extension. The current version available in CURSOR is 24.4.1 from DECEMBER or 2024. There have been significant improvements in the plugin AND a few MAJOR bug fixes.
I’m going to have to stick with base VSCODE until It catches up.
it may seem basic but its its unfortunately not. Its not update vscode, copy files and done - simple process.
