0.47 is blocking the GitHub Copilot chat window

Development scenarios are diverse.

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.

1 Like

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.

1 Like

I have reported but seems no one give us official statement for this bug or feature

Yes please! Bring it back. I used to code with both agents

What is the status of that?

This is unacceptable that Cursor is blocking Github Copilot.

I have just realized I was paying for Copilot and I can’t open the Copilot Chat. This is very unfair. @deanrie @ericzakariasson

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

I had to use both, open at the same time. Or one after the other because running both my system couldn’t take it.

Just don’t work on the same coebase with each, with the same files open.

Cursor won’t recognize the changes from VSCode, then you edit the same file in Cursor and overwrite the updates.

Major bug. Crickets from Cursor since reporting it.

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

However, they will absolutely not fix this issue