Any plans to keep up with VSCode?!

Ideas Feedback
,
1

Cursor is always waaaaaaay behind upstream VSCode. Always has been. This is going on forever.

For example, as of today VSCode is 1.111.0 Cursor is still based on 1.105.0

That is an 8 months gap. Half of my extensions don’t work cause they need a newer release.

Truth is: I only use Cursor for autocompletions. They are brilliant and they are your killer feature. Almost no one I know uses Cursor’s “agentic” stuff, since ClaudeCode and OpenCode does it better anyway.

If Cursor tries to position itself differently - as an “editor”, not just a CLI agent orchestration tool - well then please make sure the editor - you core feature - actually unbroken?

3

I can’t tell if you’re trolling or not. Cursor’s agentic tooling is best-in-class.

If you only use it for autocomplete you’re missing out.

1 Like
4

Hey Alex,

If you have some examples of extensions that have stopped working, please let us know! Even if we aren’t rebasing on a new version right away, there are things we can look at addressing re: plugin compatability.

5

Oh good, then we don’t have to keep up it with VSCode, fair point!

7

@Colin it’s this one for example. Open VSX Registry

Newest fixes require a newer version of VSCode

(And the reason I use this extension, and not Cursor’s inhouse - well, because Cursor has abandoned it, no releases in 1 year )

10

Thank you, @alex-jitbit!

Unfortunately, I don’t have any immediate good news to share. Updating VSCode compatibility is not currently in our short-term plans. However, we are actively working to bring our Cursor-published variants of some Microsoft extensions up to date!

11

Three weeks later, VSCode is now 1.114, Cursor is now 9 months behind.