GitHub Copilot, Copilot Chat and Copilot Labs Extensions Not Working in VSCodium #1546
Comments
|
I have given a try to the steps mentioned in that issue as well, but it only deals with CoPilot Nightly extension issue, and not the Copilot labs as well as Copilot chat issues. |
|
+1
Appreciate all you do maintainers. Could be that we just accept the trade off? |
|
Is this something we could help with in VSCodium at all - or should we just link the discussion issue in the wiki and close this issue? |
|
This is an issue that Copilot chat oesnt work |
|
The issue is that this extension is both proprietary and closed-source and only "blesses" the MS binaries; the question is therefore: can we do anything about this in vscodium directly - like adjusting the distributed product.json? If not then the discussion issue seems to be a better place to check what/how something works and to document the result in the wiki - like we do for other MS extensions - or place a link to the discussion there. The real solution to this issue would be of course that the extension is made public and under a free license (even if the endpoint needs online access which is stored behind an access token) and does not need any "blessing"but work on the OSS version of vscode out-of-the-box. |
|
Yes, it's possible to make Copilot Chat work by tweaking some lines in the product.json file. However, I haven't managed to do this for the VScode Figma extension🥲 We definitely need someone to explain what's going on in the product.json file. |
|
I was able to log into figma extension with duti util: |
@wtf403 Would you mind sharing what tweaks are needed to get this working? I'm using VSCodium Insider, and have the Copilot Chat extension installed. Regular Copilot features work but Chat doesn't. The extension logs for Copilot Chat say even though I am definitely logged in (since regular Copilot works). Edit: forgot to mention but I'm also in the Chat private beta. |
|
@movq Sorry, for now, I can't 🙃 |
|
I just downloaded the latest VS Codium and the latest Copilot Chat extension, and when I try to install the .vsix file, I got this error: 
|
|
not that hard to fix, edit /Applications/Visual\ Studio\ Code\ -\ Insiders.app/Contents/Resources/app/product.json 2023-07-07 21:04:37```
and rename the app from VSCodium to vscode. download zipped vsix from webstore or from
`
~/Library/Application\ Support/Visual\ Studio\ Code/CachedExtensionVSIXs
`
unzip it and edit the package.json to accept vscodium, and change min version |
|
As multiple users reported, Copilot Chat is not available (ofc I have beta access and I have it working flawlessly on VSCode Insiders). |
|
Not helpful, we're dealing with GitHub Copilot Chat extension here |
|
Hey, has anyone who has access to chat (and lab) have tried the insider edition of vscodium? It will also be nice if a link of insider to be added to README since it is not obvious that it exists. |
i have installed it but the app does not show up in the left bar |
|
I opened an issue for copilot chat. Feel free to upvote and add any details/comments to it |
Done with b667614 :-) |
|
It sends the editor version in the request to copilot, u need to edit extension.js and hardcode the editor version value in as vscode/insiders |
|
@clockcoinG1 I assume you are talking about the chat extension.js. I am going through it right now (unfortunately) but it is way too many lines and I am no expert in js. |
|
It seems like it is trying to call the getSession from the vscode module but it returned undefined. return await vscode.authentication.getSession("github", ['user:email'], {silent: !0}) ??
await vscode.authentication.getSession("github", ['read:user'], {silent: !0});this is under Seems like it is similar to microsoft/vscode-pull-request-github#1778 |
Search `Bearer ${ in extension.js ( ~/.vscode-insiders/extensions/github-copilot-chat/dist/
Here you see it pulling the version, change that to vscode/1.83.0-insider:
if it still doesnt work run it with GH_COPILOT_TOKEN, or GITHUB_TOKEN, env var and run it |
|
Hardcode editor version into the headers or edit the getEditorVersion function to return a constant.
|
|
also in /Applications/VSCodium.app/Contents/Resources/app/product.json |
|
Could someone provide a step by step explanation of that? @clockcoinG1 perhaps? Thanks to all |
|
Yeah, I tried to follow the instructions but failed to even reach the point where @clockcoinG1 got. It is possible that I might have missed something but that's as far as I got. To be fair, the version of chat I was using seems to be different from @clockcoinG1 as well so that could also be a reason. Ideally the vscode team should fix this, it will be great if you guys can upvote the issue if you haven't. |
|
I would try to just rename the app name and datadirs to vscode-insiders, and enable copilot chat in preferences /Applications/VSCodium.app/Contents/Resources/app/product.json |
|
I just managed to hack / patch VSCode OSS's
Note: (For ArchLinux-based distros) The The changes I had to make on top of this were in the following diff (note my --- a/product.json 2023-10-20 11:17:19.854726954 -0600
+++ b/product.json 2023-10-20 11:20:43.678596193 -0600
@@ -534,20 +534,26 @@
"inlineCompletionsAdditions"
],
"GitHub.copilot-chat": [
- "handleIssueUri",
"interactive",
"interactiveUserActions",
- "terminalContextMenu",
+ "chatProvider",
+ "codeActionAI",
+ "findTextInFiles",
+ "textSearchProvider",
"terminalDataWriteEvent",
+ "terminalExecuteCommandEvent",
"terminalSelection",
"terminalQuickFixProvider",
- "chatSlashCommands",
- "chatVariables",
- "chatAgents",
+ "handleIssueUri",
"readonlyMessage",
- "chatProvider",
+ "chatVariables",
"mappedEditsProvider",
- "aiRelatedInformation"
+ "aiRelatedInformation",
+ "chatAgents",
+ "chatAgents2",
+ "chatAgents2Additions",
+ "defaultChatAgent",
+ "contribSourceControlInputBoxMenu"
],
"GitHub.remotehub": [
"contribRemoteHelp",Finally, the other necessary change was to unpack the I changed it from: $ /usr/bin/code --version
1.83.0
e7e037083ff4455cf320e344325dacb480062c3c
x64Relevant part of "engines": {
"vscode": ">=1.83.0",
"npm": ">=9.0.0",
"node": ">=18.0.0"
}Steps:
|
|
@trinitronx I believe your patch file specifically calls out line |
|
Please complain at the Copilot extension that it does not work with open-source builds of vscode; if they keep changing things then they should either document what is needed or preferably add it in vscode itself. note that a newer vsix may need an insider build - You didn't try with the old vsix that previously worked, did you? |
|
I literally just installed vscodium-bin-marketplace and was able to install GitHub Copilot Chat from the VSCodium UI without any issues. No need to manually download .vsix files or manipulate a product.json file after every update. Depending on how you installed VSCodium, you might prefer one of these options:
For me (having vscodium-bin), my preferred choice was vscodium-marketplace-bin. I'm using an the latest Manjaro Linux. |
|
I installed GitHub Copilot Chat from the VSCodium UI with the visualstudio marketplace and after fixing a lot of errors with the |
|
I installed Copilot and Copilot Chat using the marketplace. I managed to get the login to work by adding "authLearnMore" into "GitHub.copilot-chat" permissions in product.json, restarting vscodium, pressing ctrl+p and ">GitHub Copilot: Sign in to Chat" and going through the auth flow. However, there is still some uncaught error that prevent the chat from working: |
|
I keep getting: |
Finally got it running. Switching to vscodium-insiders seemed to do the trick. |
|
vscodium stable |
GitHub Copilot chat released a new version of the extension just a moment ago, which might give you a message like: |
In fact, all latest versions of GitHub Copilot Chat are TOO NEW and they only show the latest 5 versions on the marketplace web site.... omg. So I needed to use: https://stackoverflow.com/questions/76211091/how-can-i-get-a-list-of-a-vs-code-extensions-versions So I could execute: Giving me: .....
{
"version": "0.14.2024031901",
"flags": 1,
"lastUpdated": "2024-03-19T09:42:12.960Z"
},
{
"version": "0.14.2024031802",
"flags": 1,
"lastUpdated": "2024-03-18T16:40:48.993Z"
},
{
"version": "0.14.2024031501",
"flags": 1,
"lastUpdated": "2024-03-15T09:31:21.830Z"
},
....I'll pick I also believe now I picked a too old version, so Copilot chat still doesn't work. And if I picked the latest version(s), it's too new for Vscodium.. Aaaahhhh Then I saw errors that it also needed the |
|
|
Copilot Chat is just not working with VScodium (just copilot does work, but not Chat):
Again, downloading the latest GitHub Copilot chat for VScodium gives me compatibilities error messages. So either way, we can't use Copilot chat. |
|
It works for me, you have to use the marketplace from VSCode and add the additional lines to your |
|
Other than the vscode marketplace, did you use something else? Which version of VSCodium and which extension(s) do you use? You mean these additions? #1546 (comment) I see no reason to not include them by default, @daiyam do you? |
@TimTheBig I am getting the same error now, how did you fix this? I'm using Copilot Chat extension |
|
As far as I know you have to use the VS code marketplace. The extension may have been updated, you might have to wait for a VSCodium update. |
|
@GitMensch, my answer from #1852
|
@TimTheBig you mean this marketplace or the built-in extensions marketplace in VSCodium UI? |
|
You have to modify your |
|
@TimTheBig Which version are you using? (VSCodium and Copilot) |
|
VSCodium: GitHub Copilot: |
|
yelp! is there a script to patch the whole thing without manual tweaks? argument1: path to product.json, argumetn2: path to /support product.json etc. spent several hours to make this work but failing miserably. installed from vscode marketplace (#1546 (comment)): 
|
What version of copilot-chat is the store page showing beside the name? |
|
For me completions worked but chat did nothing when I pressed enter, the same issue as @melroy89 (#1546 (comment)). Turns out it's a matter of matching the correct vscodium and copilot chat versions. I'll present one solution, but it may be possible to match different versions and have it work.
You're done, enjoy!
|
|
Is there a compatible Github Copilot Chat version in VSCodium version 1.93.0? |
This comment was marked as spam.
This comment was marked as spam.
|
Just out of curiosity: What is the benefit of using a using non-proprietary, non-telemetry-defaulting binary of vscode when installing a proprietary binary extension (which is likely licensed to be only used with Visual Studio Code) that talks the whole time to a service that's not under your control using non-free binaries of a non-free language model (trained on free software) which likely has several kinds of telemetry? |
|
You're right. But the idea is to reduce telemetry as much as possible. Sometimes not everything is perfect. I personally use Github Copilot because I can't find a open source model that works well. |
|
After replacing again the product.json tu use microsoft store, i was able to reinstall both extensions for copilot (standard + chat). |
|
If you are not aware - you don't need to replace the product.json but can override it per environment variable / user config file (upstream vscode sadly did not implement the PR because "they are working on providing a user endpoint" ... since some years now - so that's VSCodium only): https://github.com/VSCodium/vscodium/blob/master/docs/index.md#how-to-use-a-different-extension-gallery |
and others
Describe the bug
I am having trouble integrating GitHub Copilot and Copilot Labs extensions with VSCodium. Despite having access to GitHub Copilot X, I am unable to get it working with VSCodium. The Copilot Labs extension isn't working and the Copilot chat doesn't show up in the activity bar.
Please confirm that you have searched existing issues in the repo.
Yes, I have searched existing issues.
Please confirm that you have checked the FAQs.
Yes, I have checked the FAQs.
VSCodium version
Version: 1.79.0 (system setup)
Release: 23159
Commit: 4be06ce527f2ea3b9b3096ac4b4c5aa11c64e7a4
Date: 2023-06-08T21:27:43.604Z
Electron: 22.3.10
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.22621
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect to be able to use GitHub Copilot and Copilot Labs extensions with VSCodium without any issues.
Screenshots
(If applicable, add screenshots to help explain your problem.)
Desktop (please complete the following information):
Additional context
I have tried several troubleshooting steps, including signing in and out of GitHub Copilot, editing the product.json file, and generating a new personal access token. None of these steps have resolved the issue.
The text was updated successfully, but these errors were encountered: