I see several usability issues with the editor itself. Why is Cursor not built as an Extension, instead of a fork from VS-Code?

[image] Why not a plugin? Discussion VSCode extensions have very limited control over the UI of the editor confused Our Command-K and Copilot++ features aren’t possible as extensions. Same for much of what we want to build in the future!

something about can’t do what they need to do as a plugin but even a crippled version of cursor AI that could read the context and give me code would be good enough for me

There’s an unofficial VS Code extension, but it’s more limited: [image] GitHub - Helixform/CodeCursor: An extension for using Cursor in Visual Studio... An extension for using Cursor in Visual Studio Code. - GitHub - Helixform/CodeCursor: An extension for using Cursor in Visual Studio C…

ill try it… I dont get it though… All I really need is the answer and I can paste it in myself … I can’t debug .net and its ruining it for me

tried it… I guess no plugins in vscode are allowed to just change the files themselves

Why is Cursor not an Extension to VS-Code?

Discussions

Jakob January 25, 2024, 8:30pm 3

Topic		Replies	Views
Why not a plugin? Discussions	3	1668	January 19, 2024
Visual Studio support? Help	14	22270	October 18, 2025
VS Code extension not working on Cursor AI, though cursor is build on top of VS Code Help	0	138	July 5, 2025
Time to support JetBrain Feature Requests	2	303	April 11, 2025
Creating Extensions Feature Requests	6	4448	January 8, 2026

Why is Cursor not an Extension to VS-Code?

Related topics