Unable to use co-pilot in 0.48

[tumeden]

With the recent introduction of multi-window chat support in Cursor, particularly in version 0.48, GitHub’s Copilot Chat extension no longer loads properly—it no longer has a visible button or accessible interface. In previous versions, like 0.46, Cursor supported both Cursor Chat and Copilot Chat side by side, allowing users to seamlessly switch between them via tabs in the chat interface.

I’m asking that this functionality be brought back. I fully understand the intention to encourage users to adopt Cursor as their primary solution, but I have a real and valuable use case for using both systems in parallel. Forcing a choice between the two breaks my workflow and requires me to switch between Cursor and VSCode just to maintain productivity.

If Cursor allowed all extensions without limitation, it could truly become a one-stop solution—and people would naturally gravitate toward it. Being able to fluidly switch between chats, especially during high-demand moments, or leverage both subscriptions at full speed, is incredibly powerful. Losing that ability is a significant setback.

At the moment, my only workaround is to revert to an older version (0.46) just to retain this dual-chat capability, but that comes at the cost of missing out on newer features. Please consider re-enabling full support for Copilot Chat alongside Cursor Chat—I genuinely want to stay within the Cursor ecosystem, and this change would ensure that’s possible.

Hopefully the Tech team takes this into serious consideration,

Thanks.

[deanrie]

Hey, here’s the official response:

Re-enable Copilot or Add the Copilot Model to Cursor

VSCode started to hardcode a lot of things into vscode core that we’ve had to change that was breaking core cursor functionality unfortunately. Its not as easy as just installing the extension, we have to actually implement support for copilot. What is the importants of using Copilot for you? Our hope is that everything we offer is simply bettere than Github Copilot and people have no need for it.

[tumeden]

Thanks for the follow-up. I totally get that deeper Copilot integration might be complex, but I’m not asking for full support of the entirety of the co-pilot ecosystem —just that Copilot Chat be allowed to co-exist like it did before. Right now, the only thing breaking it is that Cursor no longer provides a space for the Copilot chat window to render—leading to runtime errors. That interface used to work fine in earlier versions alongside Cursor Chat.

All I’m really asking is for the chat panel to be re-enabled so Copilot Chat has a place to live. No need to integrate it deeply—just let it run as it used to. That small change would restore a ton of flexibility for those of us who rely on both tools.

Really hoping this can be considered. I love what Cursor is building, and I’d much rather stay in Cursor than juggle environments just to access both chats.