Cursor based on vscode, it cannot solve all problems. Jetbrains IDE, XCode, and Visual Studio are areas where Cursor cannot reach, while Github Copilot can work in these scenarios.
If it’s just a competitive relationship, choosing to make the already paid Copilot unusable on Cursor cannot prevent users from paying for Copilot.
I hope Cursor can choose to provide plugin support for other IDEs, or adopt an open attitude to support Copilot.
For someone who works across various development environments, I can use another vscode to use Copilot. Ultimately, Cursor has created inconvenience for users, led to wasted memory resources, and users are still subscribed to Copilot.
I share the same view as you. I don’t think that integrating Block Copilot into Cursor will make people pay for Cursor. On the contrary, it will lead to the loss of users.
Paid Copilot cannot be used on VSCode-based Cursor, which is simply ridiculous. So Microsoft disabled you from using their plugin? Making users abandon you
They either avoid the topic, tell you their technology isn’t capable of making the two work together, or boast about how great their work is and how VS Code is the problem causing this situation