-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copilot not working in Remote windows #236537
Comments
A fix will be release in the next official Insiders build, followed by a recovery build for Stable. |
@sandy081 and me investigated further and there are 2 issues with 2 changes planned:
The fix is to query extensions without duplicates (local, remote) and only check for enablement of the one in the remote if connected to a remote: #236552 This is the same fix @roblourens did: acd32b1 A variant of the above to reproduce is for users that simply have Copilot already installed locally and connect to a remote. In that case the local one would get disabled and thus reproduces this issue too (for example connecting to a Codespace).
The fix for that bug also goes into #236552 |
…talled locally if `installEverywhere` is set
Test Plan Item Testing should be done with fresh user data dir and fresh extensions dir on stable build. Local1.) without copilot extensions installed ✅ @sandy081 and @bpasero
2.) with copilot extension installed ✅ @sandy081 and @bpasero
3.) with copilot extension installed but disabled ✅ @sandy081 and @bpasero
Remote: SSH / Devcontainers / WSL / Codespace1.) without copilot extensions installed
2.) with copilot extension installed locally
3.) with copilot extension installed remotely
4.) with copilot extension installed locally and remote
5.) with copilot extension disabled remotely
6.) with copilot extension installed locally and remotely but disabled
SSH - ✅ @sandy081 and @bpasero |
- Support installEveryWhere option by installing the extension only on servers on which it is not installed
After reading your previous answer, I jus !t kept the Github Copilot extension on the local app, and not WSL. Thanks |
This comment has been minimized.
This comment has been minimized.
This should be fixed in the 1.96.2 release. |
This is a duplicate issue to microsoft/vscode-copilot-release#3375 for information purposes only.
When using Copilot in with DevContainer, SSH, or WSL you will encounter that the Copilot Chat window is stuck in the setup state. The recording below shows the error state as well as a temporary workaround.
The error state is that the Chat window displays a button to suggests to you to "Use Copilot" or "Use Copilot for Free". When clicking the button, supposedly nothing happens.
The workaround:
The workaround is necessary for each remote window.
We're working on a fix.
This issues was first reported as microsoft/vscode-copilot-release#3366.
The text was updated successfully, but these errors were encountered: