Copilot Chat not working (failed to login) for OSS build of VSCode (VSCodium)

[Neko-Box-Coder]

Select Topic Area

Bug

Body

I am having trouble trying to get Copilot chat working for VSCodium (OSS version of VSCode) despite Copilot and Copilot lab are signed in and working.

I tried the .vsix on VS market place but it seems like it requires the insider version of VSCode to work.
So I installed copilot chat by adding the VS marketplace instead and it managed to install.

However, it shows that it fails to sign in to github in the output and the chat window is also missing. Here is the output I have.

2023-09-29T01:52:42.337Z [INFO] [auth] GitHub login failed
2023-09-29T01:52:42.338Z [ERROR] [extension] {"constructionStack":["    at new t.ServicesAccessor (/home/user/.vscode-oss/extensions/github.copilot-chat-0.7.1/dist/extension.js:2:1262828)","    at t.createProductionContext (/home/user/.vscode-oss/extensions/github.copilot-chat-0.7.1/dist/extension.js:2:1007003)","    at Y (/home/user/.vscode-oss/extensions/github.copilot-chat-0.7.1/dist/extension.js:2:1604401)","    at e.activate (/home/ed/.vscode-oss/extensions/github.copilot-chat-0.7.1/dist/extension.js:2:1607510)","    at Function._callActivateOptional (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:118:16763)","    at Function._callActivate (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:118:16429)","    at /opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:118:14236","    at y._activate (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:107:7862)","    at y._waitForDepsThenActivate (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:107:7804)","    at y._initialize (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:107:7168)"],"instances":{},"isSealed":false},You are not signed in to GitHub. Please sign in to use Copilot.

Here are the versions for everything:

• OSS VSCode (VSCodium): 1.82.2
• Copilot: v1.115.431
• Copilot Chat: v0.7.1
• Copilot Labs: v0.15.1019

Also see VSCodium/vscodium#1546 for more details.

If there's any other information needed in order to solve this issue, please let me know

[Neko-Box-Coder]

It would be appreciated if anyone on the VSCode/Copilot Chat team could give any feedback on this issue as other Copilot plugins seem to work just fine.

[moayad-star]

It appears that the issue you're facing is related to Copilot Chat's inability to sign in to GitHub. Here are some steps you can try to resolve this problem:

1. Check GitHub Credentials: Make sure you are signed in to GitHub using the same account that you intend to use with Copilot Chat. Sometimes, this can be an issue if there are multiple GitHub accounts associated with your VSCode.

2. Update Extensions: Ensure that both Copilot and Copilot Chat are up to date. Sometimes, issues like these are resolved in newer versions of the extensions.

3. Review GitHub Token: Copilot Chat may require a GitHub token for authentication. Check if there's an option to provide a GitHub token in the extension settings and make sure it's correctly configured.

4. Check Permissions: Ensure that the VSCode installation (VSCodium in your case) and the Copilot extensions have the necessary permissions to access your GitHub account. This can usually be configured in your GitHub settings under "Authorized OAuth Apps."

5. GitHub Status: Occasionally, GitHub services may experience downtime or issues. Check the GitHub Status page to see if there are any ongoing incidents that might be affecting the authentication process.

6. GitHub Two-Factor Authentication: If you have two-factor authentication (2FA) enabled on your GitHub account, make sure you're using a personal access token (PAT) instead of your password for authentication within Copilot Chat.

7. Extension Conflicts: It's possible that another VSCode extension might be conflicting with Copilot Chat. Try disabling other extensions one by one to see if any of them are causing the issue.

8. GitHub Organization Permissions: If you are using GitHub as part of an organization, ensure that your organization settings allow the Copilot Chat extension to access the necessary repositories.

9. Reinstall: If none of the above steps work, you can try uninstalling Copilot Chat, restarting VSCode, and then reinstalling it to see if it resolves the issue.

Remember to save your work and configuration settings before making significant changes to your VSCode setup. If the issue persists after trying these steps, consider reaching out to the Copilot Chat support or checking for community discussions related to this specific problem, as it might be a known issue with the extension.

[moayad-star]

I don't know, but this is what I found ChatGPT :
I apologize for the continued issue you're facing with Copilot Chat in VSCodium. If you've already checked the following points and the problem persists:

1. GitHub Token: If there's no specific option to provide a GitHub token in Copilot Chat's settings, it's possible that the extension should automatically authenticate through the GitHub OAuth flow. Since you mentioned it fails to sign in, it might be a bug or limitation in the extension's interaction with VSCodium.

2. GitHub Status: If the issue is specific to Copilot Chat in VSCodium and not affecting Microsoft's distributed VSCode, it could be a compatibility issue between the extension and the OSS version of VSCode. Copilot Chat might be designed and tested primarily for the official VSCode.

3. Support: If you've already checked community discussions and haven't found a solution, and if the issue persists even after contacting Copilot through their issue page, it's possible that this specific compatibility problem hasn't been widely addressed yet.

In this case, you might need to wait for a potential update from the Copilot Chat developers that addresses compatibility with VSCodium or consider using Microsoft's VSCode until the issue is resolved. Additionally, you can continue monitoring the GitHub issue page and community discussions for any updates or workarounds that might emerge.

I understand this may not be the ideal solution, but it seems like you've explored most of the available troubleshooting steps, and the issue might require specific attention from the extension developers or the VSCodium community to resolve.

**But my advice try posting a problem on https://stackoverflow.com/. Surely there is someone who can solve it **

[moritztim]

This is not helpful! Don't just go asking chatgpt, we can do that ourselves.

[moritztim]

ChatGPT doesn't have enough context to actually help.

[ghostinhershell]

Hi @moayad-star,

We’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team.  You can read our updated Code of Conduct and the announcement for more details. Thank you for helping us maintain an authentic and beneficial space for everyone.

[moritztim]

Do not just post AI-generated content verbatim to inflate your reputation or give a false impression of product expertise.

[gursheyss]

This worked for me
VSCodium/vscodium#1546 (comment)

[Neko-Box-Coder]

Yeah, we seem to be able to get it working now by modifying the proposed API mentioned linked above.
For details on modifying product.json, you can either modify the one in the install location or in the config location mentioned here

https://github.com/VSCodium/vscodium/blob/master/docs/index.md#how-to-use-a-different-extension-gallery

It is actually quite disappointing that there is zero support from the github copilot (chat) team to give any direction on getting it working on the open source version of vscode, despite we the users have paid for the service.

[gjedeer]

Is Microsoft seriously expecting paid customers to go through patching files just to get the product working? And it's not working for me, probably my fault, but it feels like Copilot is a hack not a product

[zuhairnaqi]

Hi, just check you've enable the cloud changes using Github account, this fixed my issue

[fengerzh]

Thank you! This is the only and easiest and correct way to solve the issue.