Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:
Check the forum to ensure the issue hasn’t been reported already Provide a clear description of the bug Explain how to reproduce the bug (if known) Attach screenshots or recordings (e.g., .jpg, .png, .mp4). Tell us your operating system and your Cursor version (e.g., macOS, 0.47.x). Tell us if the issue stops you from using Cursor.
GitHub Copilot is a highly useful feature on the GitHub website, and it also allows opening multiple chat windows in VSCode, serving as a valuable supplement to Cursor. If Cursor were to forcibly disable this feature, I would have to resort to using the less capable older version of Cursor until the Copilot agent catches up, at which point I would no longer use Cursor.
With minimal changes, gh copilot chat can now run on w-indsurf. If the disabling of copilot in cursor becomes a reality, I will switch to w-indsurf in the next subscription cycle
I’m seriously considering moving to another tool if Cursor doesn’t restore GH copilot functionality quickly. It feels very shady that it is the only vscode extension that doesn’t work.
On top of that, I subscribe to both and I like to have both in the same IDE mainly because Cursor has become almost unusable in the last releases and Copilot is the falback
Cursor is not to blame for this Github Copilot has completely changed the way their extension works over the last month lot’s of unannounced changes.
They’ve added rate-limits and a limited number of premium RPM for models except GPT-4o which is unlimited still and are limiting Copilot to only work with their official VSCode Insiders implementation of Copilot, you cannot even use VS LM API anymore in Cline or Roo for anything but GPT and O-models.
This is not a Cursor issue but a Microsoft/Github issue, it’s very likely Copilot may become integrated directly only into the official VSCode app.
Their website also heavily implies that starting soon Copilot Pro will almost double in price to $19. I cancelled my GH Copilot sub already and will be switching fully back to Cursor.
From the timeline perspective: first, cursor blocked copilot, and now the vs C++ plugin in the vscode extension marketplace cannot be used in third-party vscodium
This approach is akin to the China and US trade tariff war
But it was cursor that disabled copilot first, cursor started the war
You cannot bypass the VS LM API restrictions, if you do you get banned from using Github Copilot. People did it and GH is mass banning them for TOS violations.
Copilot is changing and going forward it is only going to become more and more restricted to Official VSCode only
Also the workbench changes are by VSCode they are heavily more integrating Github Copilot into VSCode, if you want to use Copilot’s new agent mode for example you have to use VSCode Insiders Edition to be able to access it, when I say going forward a lot of VSCode features will simply not work outside of Official VSCode versions I mean it.
Microsoft’s goal is to have users restricted to using only GH Copilot in VSCode, not Roo, Cline or Codium. Not other VS Forks with their own AI integration.
Review everything Github, VSCode and Microsoft have said but none of this is bugs, simply deliberate changes to enhance Microsoft’s VSCode’s position moving forwards.
The solution you mentioned that gets GH banned is likely copilot-more (I myself have been banned before). However, the freedom solution mentioned above cannot be detected by the official system, as it removes the official identification fields. After the official cancellation of unlimited usage, this solution theoretically will no longer be restricted. So far, the freedom project has been used by a large number of people, including myself, and despite triggering rate limits multiple times, it has not been banned.
Agent has been released in the stable version of VSCode and no longer requires the Insider version. VSCode now supports JetBrains, Xcode, and GitHub Web simultaneously. Also supports BYOK.
Since Cursor does not support JetBrains and others in the form of plugins, Copilot has become a must-subscribe product for me, as my development environments are highly diverse.
After version 0.47, Cursor blocking Copilot is not caused by VSCode but by Cursor’s forced blocking. The latest self-compiled version of VSCodium-OSS can still launch Copilot Chat. We should not unfairly blame VSCode for what Cursor does—it’s unethical.
I have subscribed to Cursor, Copilot, and Augment simultaneously, and with deep usage, I can exhaust Cursor’s 500 quota in just 7 days.
Check the forum to ensure the issue hasn’t been reported already
Provide a clear description of the bug
Explain how to reproduce the bug (if known)
Attach screenshots or recordings (e.g., 
Tell us your operating system and your Cursor version (e.g., 
Tell us if the issue stops you from using Cursor.