[GUIDE] 2025 How to run Copilot in VSCodium (without VSCode) #1487
Replies: 52 comments 93 replies
-
Why do we have to use that specific client_id? I found it a big sketchy, but it did work! |
Beta Was this translation helpful? Give feedback.
-
I needed to use Git Bash on Windows for |
Beta Was this translation helpful? Give feedback.
-
Works like a charm on Powershell v7 without any hassle. Thank you! |
Beta Was this translation helpful? Give feedback.
-
Heck yeah! Thanks for that dude 🔥 |
Beta Was this translation helpful? Give feedback.
-
Flatpak usersStill working for me as of 2024-08-01I installed VSCodium on
Thanks, @ustas-eth ! |
Beta Was this translation helpful? Give feedback.
-
I'm having trouble activating Github Copilot Labs with this trick. Can it be done? Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
How do we find out where |
Beta Was this translation helpful? Give feedback.
-
This worked on my Linux laptop, much love. I was just wondering why on the Windows Binary for VSCodium the "official" login for GitHub Copilot works on my end? Is there some f*ckery because it is a Windows machine and Windows authenticates me anyway like that? |
Beta Was this translation helpful? Give feedback.
-
as of Jun 22 this still works thank you so much |
Beta Was this translation helpful? Give feedback.
-
This is just amazing. Thanks a lot. The only issue I have right now is that I have to keep logging in to GitHub on VSCodium each time I open it. Any way to fix this problem? |
Beta Was this translation helpful? Give feedback.
-
Umm, Where should i paste my access token ? (Step 7) |
Beta Was this translation helpful? Give feedback.
-
On Manjaro Linux (so should work for Arch as well) I found $ sudo pacman -Ql vscodium | grep product.json
vscodium-bin /opt/vscodium-bin/resources/app/product.json |
Beta Was this translation helpful? Give feedback.
-
Works on Linux Mint, using VSCodium installed from the Ubuntu repository. Thanks @ustas-eth ! SnapIn case anyone installed VSCodium using Snap, you'll need to use a workaround like described here, to edit Rather than doing that I just reinstalled from the VSCodium Ubuntu repository instead. Possible edits to original post@ustas-eth perhaps to clarify step 6 a bit further, As below:
|
Beta Was this translation helpful? Give feedback.
-
If you already installed copilot and want to use this wonderful trick, you will first have to sign out from Github using the Sign out option on the bottom left corner (the person button below the setting button). |
Beta Was this translation helpful? Give feedback.
-
Hi, I have run the following: flatpak --user install -y flathub com.vscodium.codium
flatpak --user override --socket=wayland com.vscodium.codium
flatpak run com.vscodium.codium --install-extension ~/Downloads/GitHub.copilot-1.95.246.vsix
cd ~/.local/share/flatpak/app/com.vscodium.codium/current/active/files/share/codium/resources/app
sed -e 's|"GitHub.copilot":.*|"GitHub.copilot": ["inlineCompletions","inlineCompletionsNew","inlineCompletionsAdditions","textDocumentNotebook","interactive","terminalDataWriteEvent"],|' \
-i.bak product.json I had to copy the following libraries in order for the "Sign in with Github to use Github Copilot" to appear:
in If I click on "Sign in with Github to use Github Copilot", I can generate the PAT, copy it to but I get the following error in the Developer console: workbench.desktop.main.js:97 [Extension Host] [ERROR] [default] [2023-07-09T14:39:57.595Z] GitHub Copilot could not connect to server. Extension activation failed: "Cancelled"
I @ workbench.desktop.main.js:97
$logExtensionHostMessage @ workbench.desktop.main.js:1541
_doInvokeHandler @ workbench.desktop.main.js:1541
_invokeHandler @ workbench.desktop.main.js:1541
_receiveRequest @ workbench.desktop.main.js:1541
_receiveOneMessage @ workbench.desktop.main.js:1541
(anonymous) @ workbench.desktop.main.js:1541
invoke @ workbench.desktop.main.js:93
deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:564
ee.onmessage @ workbench.desktop.main.js:1642
workbench.desktop.main.js:759 Writing login information to the keychain failed with error 'GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable'.
onDidChangeNotification @ workbench.desktop.main.js:759
(anonymous) @ workbench.desktop.main.js:759
invoke @ workbench.desktop.main.js:93
deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
addNotification @ workbench.desktop.main.js:759
notify @ workbench.desktop.main.js:1644
prompt @ workbench.desktop.main.js:1644
(anonymous) @ workbench.desktop.main.js:2526
emit @ VM4 sandbox_bundle:2
onMessage @ VM4 sandbox_bundle:2
workbench.desktop.main.js:97 [Extension Host] rejected promise not handled within 1 second: Error: User not authorized
I @ workbench.desktop.main.js:97
$logExtensionHostMessage @ workbench.desktop.main.js:1541
_doInvokeHandler @ workbench.desktop.main.js:1541
_invokeHandler @ workbench.desktop.main.js:1541
_receiveRequest @ workbench.desktop.main.js:1541
_receiveOneMessage @ workbench.desktop.main.js:1541
(anonymous) @ workbench.desktop.main.js:1541
invoke @ workbench.desktop.main.js:93
deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:564
ee.onmessage @ workbench.desktop.main.js:1642
workbench.desktop.main.js:97 [Extension Host] stack trace: Error: User not authorized
at /home/user/.var/app/com.vscodium.codium/data/codium/extensions/github.copilot-1.95.246/extension/src/auth.ts:52:15
at process.copilotToken (node:internal/process/task_queues:96:5)
at forceNormal [as getCopilotToken] (/home/user/.var/app/com.vscodium.codium/data/codium/extensions/github.copilot-1.95.246/extension/src/auth.ts:92:18)
at event (/home/user/.var/app/com.vscodium.codium/data/codium/extensions/github.copilot-1.95.246/extension/src/session.ts:53:28)
at /home/user/.var/app/com.vscodium.codium/data/codium/extensions/github.copilot-1.95.246/extension/src/extension.ts:162:46
I @ workbench.desktop.main.js:97
$logExtensionHostMessage @ workbench.desktop.main.js:1541
_doInvokeHandler @ workbench.desktop.main.js:1541
_invokeHandler @ workbench.desktop.main.js:1541
_receiveRequest @ workbench.desktop.main.js:1541
_receiveOneMessage @ workbench.desktop.main.js:1541
(anonymous) @ workbench.desktop.main.js:1541
invoke @ workbench.desktop.main.js:93
deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:564
ee.onmessage @ workbench.desktop.main.js:1642
workbench.desktop.main.js:1978 [GitHub.copilot]User not authorized
$onExtensionRuntimeError @ workbench.desktop.main.js:1978
_doInvokeHandler @ workbench.desktop.main.js:1541
_invokeHandler @ workbench.desktop.main.js:1541
_receiveRequest @ workbench.desktop.main.js:1541
_receiveOneMessage @ workbench.desktop.main.js:1541
(anonymous) @ workbench.desktop.main.js:1541
invoke @ workbench.desktop.main.js:93
deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:564
ee.onmessage @ workbench.desktop.main.js:1642
workbench.desktop.main.js:1978 Error: User not authorized
at /home/user/.var/app/com.vscodium.codium/data/codium/extensions/github.copilot-1.95.246/extension/src/auth.ts:52:15
at process.copilotToken (node:internal/process/task_queues:96:5)
at forceNormal [as getCopilotToken] (/home/user/.var/app/com.vscodium.codium/data/codium/extensions/github.copilot-1.95.246/extension/src/auth.ts:92:18)
at event (/home/user/.var/app/com.vscodium.codium/data/codium/extensions/github.copilot-1.95.246/extension/src/session.ts:53:28)
at /home/user/.var/app/com.vscodium.codium/data/codium/extensions/github.copilot-1.95.246/extension/src/extension.ts:162:46
$onExtensionRuntimeError @ workbench.desktop.main.js:1978
_doInvokeHandler @ workbench.desktop.main.js:1541
_invokeHandler @ workbench.desktop.main.js:1541
_receiveRequest @ workbench.desktop.main.js:1541
_receiveOneMessage @ workbench.desktop.main.js:1541
(anonymous) @ workbench.desktop.main.js:1541
invoke @ workbench.desktop.main.js:93
deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:564
ee.onmessage @ workbench.desktop.main.js:1642 Is an older version required? Thanks |
Beta Was this translation helpful? Give feedback.
-
It worked for me just installing the extension manually from the binary; no need for other tweaks. Ubuntu 24.04. |
Beta Was this translation helpful? Give feedback.
-
The only thing not working for me, is git commit generating messages. It seems to worked before. Anyone got a solution? |
Beta Was this translation helpful? Give feedback.
-
To install copilot go to the extension's page in the vscode marketplace, then go to the Version History tab, and download the latest version (or any other if you prefer). You're gonna get a
or click on the 3 dots in the Extensions section, and choose Then just follow the instructions to log into Github as you'd do normally. |
Beta Was this translation helpful? Give feedback.
-
I got the extension to install and auth'd my github account on my Mac, running VSCodium Version: 1.92.1 but still dont have the chat extension to allow me to actually use CoPilot. |
Beta Was this translation helpful? Give feedback.
-
Works great for anyone on Arch |
Beta Was this translation helpful? Give feedback.
-
Where is this folder with the product.json ? I could not find it in my home dir and dont assume it would be anywhere else? Fedora, RPM from repo |
Beta Was this translation helpful? Give feedback.
-
I managed to install it, but how do I actually use it? The GitHub CoPilot Chat extension is not automatically installed with it and doesn't work to manually install. So now I don't see a way to actually use this GitHub CoPilot extension? |
Beta Was this translation helpful? Give feedback.
-
still not work with Windows 10 + Vscodium (1.96.2) + Copilot latest. |
Beta Was this translation helpful? Give feedback.
-
The icon is not showing up anymore in the sidebar. Chat still works, but you have to open it through the menu. None of the solutions in this thread work anymore. (I'm using vscodium 1.96.2 on Manjaro Linux) |
Beta Was this translation helpful? Give feedback.
-
Thanks for the tips. I have it installed but the top chat menu all are grayed out. |
Beta Was this translation helpful? Give feedback.
-
This isn't working currently, right? I am able to go through the first 3 steps and get up to step 5 from the optional 5 steps. But after copying the access token from the terminal I'm not able to paste it into VSCodium. Even after login out from my GitHub account and back in... |
Beta Was this translation helpful? Give feedback.
-
Whilst the Copilot plugin is undoubtedly cool, be aware that using it from VSCodium may not be legal. Maybe you care, maybe you don't, but at least be aware of opinion and make your judgement. |
Beta Was this translation helpful? Give feedback.
-
TL;DR Solved I just tried to install Copilot with the first three steps from the instructions, and some parts of the functionality worked fine with the free version (I'm not paying anymore): I couldn't open the chat or use some other features. I wasn't able to find any errors in the developer tools. Then I found the mention of copilot-chat extension in the README of the main extension. I'm not sure how it was managed before, but it seems you need to download it separately now. Another issue I encountered was that I couldn't find the button to download the vsix file anymore. Direct links still work, though! So, I downloaded the second extension to get the chat window, but the latest version seems to only work with a future build of VSCode, 1.97.0 (the current latest is 1.96.4). I went to the Web Archive to get the number of the previous release but wasn't able to due to the service limitations, it didn't capture the block with the version number :') The good news is that their versions are derived from dates, and they are quite frequent, so I was able to bruteforce a bit and find the one that works. There was some other issue with the authorization, but all I had to do was to open the chat through the copilot icon here and click the sign in button: To have the chat as previously in the left panel, just drag this icon to the panel: The main extension: copilot-chat (the older version, worked): copilot-chat (the actual version, didn't work): Linux, Flatpack, VSCodium 1.96.2, Copilot 1.257.1316 |
Beta Was this translation helpful? Give feedback.
-
This still doesn't bring the sidebar Icon back. |
Beta Was this translation helpful? Give feedback.
-
Latest version of GitHub Copilot and Chat work on the newest version of VSCodeium Insiders edition. Tested myself and all is good. |
Beta Was this translation helpful? Give feedback.
-
The instruction
a) you can try to download the vsix files here: Copilot and Copilot Chat
b) or, if not available, by the direct links:
Copilot:
https://marketplace.visualstudio.com/_apis/public/gallery/publishers/GitHub/vsextensions/copilot/1.257.1316/vspackage
Copilot Chat:
https://marketplace.visualstudio.com/_apis/public/gallery/publishers/GitHub/vsextensions/copilot-chat/0.23.2024120501/vspackage
These links can be outdated, check the marketplace and replace
1.257.1316
and0.23.2024120501
in them if you want to download newer versions.Install them in the Extensions menu -> three dots -> Install from VSIX...
Edit
VSCODIUM_FOLDER/resources/app/product.json
. Find theGitHub.copilot
and insert the following permission:Troubleshooting
Check this post where I set it up myself: #1487 (comment)
The old way to authorize in previous versions of VSCodium:
spoiler
device_code
anduser_code
in the responseuser_code
YOUR_DEVICE_CODE
with thedevice_code
you got in step 2):access_token
in the response (gho_...
). Paste it in VSCodium when the Copilot extension requires authorization.Possible paths for the
product.json
:/opt/vscodium-bin/resources/app/product.json
/usr/share/codium/resources/app/product.json
/Applications/VSCodium.app/Contents/Resources/app/
/snap/codium/current/usr/share/codium/resources/app/product.json
Beta Was this translation helpful? Give feedback.
All reactions