[GUIDE] 2026 How to run Copilot in VSCodium (without VSCode) #1487
Replies: 93 comments 190 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.jsonI 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:1642Is an older version required? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Can't log in to github, error: Note: See the error log in Help → Toggle Developer Tools ㅤ
Thank you, it worked. ㅤ How to Install & Run GitHub Copilot in VSCodium
Tips:
ㅤ Note: at the time of writing. $ codium --version
1.103.15418
2ae20ed17e7533b35fc012f4ad1a156fd763afb2
x64
$ codium --list-extensions --show-versions | grep github.copilot
github.copilot@1.356.1735
github.copilot-chat@0.30.1ㅤ |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Goodby VSCode or VSCodium, with Copilot AI. I'm using CURSOR now. it's very enjoy. |
Beta Was this translation helpful? Give feedback.
-
|
Copilot Chat is on Open VSX now, link |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Yes read a few posts back where you initially use the old plugin version.
Then just upgrade.
If not working check rights and remove cache etc. See my previous post for
details. And honestly, since the plug-in is able to access everytin your
IDE and likely outside and requires access to your Github, one might as
well run vscode if this is the main thing you want. You can also use things
like Windsurf or other plugins that do similar things. I have it working
with latest plugins but it is mostly red because I am 'out of credits', so
it's barely useful to me personally. And last but not least, Grok is
simply much better at coding and I beleive Claude now has file support to
pre run code. Good luck!
…On Sat, 13 Sept 2025, 22:25 sallymanda, ***@***.***> wrote:
Can't get it to move beyond the sign in page in vscodium... any
suggestions? I tried the "troubleshooting" old method of authorisation, but
no dialogue requesting the access token appears :-/
—
Reply to this email directly, view it on GitHub
<#1487 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGB3CM77Q2Z3Z5ZZP6OVJT3SR4SHAVCNFSM6AAAAAAXC72ZM6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZZGMYDIOA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
"This extension is no longer available on the Extension Marketplace." I just tried today and this looks dead. I have the old version installed, but it seems dead. The link I got it from shows nothing any more: Any news about what happened? Am I forced to use the official vscode or enable microsoft marketplace? |
Beta Was this translation helpful? Give feedback.
-
|
Or use Gemini because it's so much better and just works. You could switch
to marketplace but it might not be according the Microsoft regime, as in
not allowed by license.
…On Mon, 1 Dec 2025, 23:24 Nicholas Dietz, ***@***.***> wrote:
"This extension is no longer available on the Extension Marketplace."
I just tried today and this looks dead. I have the old version installed,
but it seems dead.
The link I got it from shows nothing any more:
https://open-vsx.org/extension/GitHub/copilot-chat
Any news about what happened?
Am I forced to use the official vscode or enable microsoft marketplace?
—
Reply to this email directly, view it on GitHub
<#1487 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGB3CNXTLPIK6DP3GGWUCD37S5ZVAVCNFSM6AAAAAAXC72ZM6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJSHEYTMNY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Everyone with problems, not making copilot work, etc, there is a more updated guide in the official VSCodium wiki https://github.com/VSCodium/vscodium/blob/master/docs/ext-github-copilot.md |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I'm trying to install the extension in latest VS Codium and getting this : 1. for extension version : 0.37.6and the extension page reads :
2. for extension version : 0.35.2and the extension page reads :
and below are the modifications I've done in product.json : What am I doing wrong? What to do now? |
Beta Was this translation helpful? Give feedback.
-
|
I've been trying to figure this out as well. As of today, GitHub.copilot-chat-0.37.6 seems to work in VSCodium 1.109.51242. I'm on Windows 11, just in case you were wondering. But one thing, just a tiny little detail, that I haven't been able to find in this guide: what is next? I mean it needs to login, obviously. Where/how do I make it login? On the output pane it says: But it never offers a UI to login 🤨 There is no login or account bollocks in the settings either. Where is it?? Well, for those of you trying to figure this out as well, run the "Focus on chat view" command in VSCodium, and then just enter any prompt. Not before then, it'll ask to login. It allows you to login with Github, but also some other providers. But I've been told Github login is required for this to work, so I'm not sure why it offers anything else. Anyway, the trick is to send a prompt, anything will do like "Can you help me?" and that will trigger the authentication flow. One thing to note: I'm trying this out with Github Copilot Free. Hopefully shortly, I should be granted access to Copilot Business. This should not matter for the extension and/or the authentication flow, but if it does, I'll report back. |
Beta Was this translation helpful? Give feedback.
-
|
tl;dr: Latest VSCodium + latest copilot-chat (non-pre) release may work always together? Maybe I was just lucky, but I simply chose the latest official release and not a pre-release (0.39 are only pre-releases) and that worked for me. The latest official release is https://github.com/microsoft/vscode-copilot-chat/releases/tag/v0.38.2. VSIX download: https://marketplace.visualstudio.com/_apis/public/gallery/publishers/GitHub/vsextensions/copilot-chat/0.38.2/vspackage And it worked to install the VSIX with the latest version of VSCodium (1.110.11607). After the successful installation of the extension I signed out of all my GH accounts by clicking on the "person" icon in the bottom left corner of VSCodium. Then I restarted VSCodum, signed in again through the copilot icon in the bottom right corner. After that it tells me that it failed to find the copilot-chat extension and install it, I clicked twice on "cancel" and now everything works fine. |
Beta Was this translation helpful? Give feedback.
-
|
Finally now vsix is oficially release on their github repo :D Also latest ver is working on insider :b |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ustas-eth, |
Beta Was this translation helpful? Give feedback.












Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
New!
VSIX were finally released in the official repo, download them and install manually in the tab, it seems there may only be issues with the latest version due to a lag in VSCodium updates so you may need to install some of the older ones.
https://github.com/microsoft/vscode-copilot-chat/releases
See these comments and give merit to the good people who keep the guide updated:
#1487 (comment)
#1487 (comment)
Old!
the prev shaman way
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.1316and0.23.2024120501in 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.copilotand 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_codeanduser_codein the responseuser_codeYOUR_DEVICE_CODEwith thedevice_codeyou got in step 2):access_tokenin 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.jsonBeta Was this translation helpful? Give feedback.
All reactions