Chat not working in Codespaces #189290
Replies: 10 comments 7 replies
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Hi, The error in your log is the key part here: This usually means that a downloaded package or extension is corrupted or incomplete. In Codespaces this commonly happens when the VS Code server extensions cache becomes inconsistent after an update. Since Copilot Chat was recently updated, the Codespace may still have an older or partially downloaded version of the extension. Here are a few things you can try: 1. Restart the CodespaceSometimes the VS Code server just needs to reload:
This forces the VS Code server to reinitialize. 2. Reinstall the Copilot Chat extensionInside the Codespace:
This will trigger a fresh download of the extension. 3. Rebuild the Codespace containerIf the extension cache is corrupted, rebuilding the container usually fixes it. You can do this from: Documentation: 4. Update VS Code server componentsYour message indicates that the current environment is using 38.2 and is suggesting an upgrade to 39. If the upgrade failed during download, the server components may be partially installed. Rebuilding the Codespace usually resolves this. SummaryThe error is typically caused by a corrupted extension download or incomplete VS Code server update inside the Codespace. Restarting the Codespace or rebuilding the container usually forces a clean install and restores Copilot Chat. Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
|
We are using codespaces for a training for a class. Of ~20 people in the class, we found this error to be happening roughly 80% of the time. Deleting and recreating the codespace had a roughly 20% chance of succeeding, as well. |
Beta Was this translation helpful? Give feedback.
-
|
facing same issue |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I found later that I am not able to install reinstall or update ANY plugin,
including copilot chat, even on completely NEW codespace container. The
chat is not able to initialize on a completely new codespace container.
Can a connected repository affect this in any way?
Regards,
Dejan
…On Thursday, March 12, 2026, Angel Villafuerte ***@***.***> wrote:
Hi,
The error in your log is the key part here:
End of central directory record signature not found.
Either not a zip file, or file is truncated.
This usually means that a downloaded package or extension is *corrupted
or incomplete*. In Codespaces this commonly happens when the *VS Code
server extensions cache* becomes inconsistent after an update.
Since Copilot Chat was recently updated, the Codespace may still have an
older or partially downloaded version of the extension.
Here are a few things you can try:
------------------------------
1. Restart the Codespace
Sometimes the VS Code server just needs to reload:
- Stop the codespace
- Start it again from the repository page
This forces the VS Code server to reinitialize.
------------------------------
2. Reinstall the Copilot Chat extension
Inside the Codespace:
1. Open *Extensions*
2. Search for *GitHub Copilot Chat*
3. Uninstall it
4. Install it again
This will trigger a fresh download of the extension.
------------------------------
3. Rebuild the Codespace container
If the extension cache is corrupted, rebuilding the container usually
fixes it.
You can do this from:
Codespaces → Rebuild Container
Documentation:
https://docs.github.com/en/codespaces/developing-in-
codespaces/rebuilding-the-container-in-a-codespace
------------------------------
4. Update VS Code server components
Your message indicates that the current environment is using *38.2* and
is suggesting an upgrade to *39*. If the upgrade failed during download,
the server components may be partially installed.
Rebuilding the Codespace usually resolves this.
------------------------------
Summary
The error is typically caused by a *corrupted extension download or
incomplete VS Code server update inside the Codespace*. Restarting the
Codespace or rebuilding the container usually forces a clean install and
restores Copilot Chat.
Hope this helps.
—
Reply to this email directly, view it on GitHub
<#189290 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFT6PIB3RCAAO2KFQCGFNIL4QKAOLAVCNFSM6AAAAACWPDSJIGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBZGU2DKMA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
OK! I found out what impacts my codespaces.. When I switch off dotfiles - everyhting works. When I turn them on - codespaces are broken and indeed none of extensions can be installed.. |
Beta Was this translation helpful? Give feedback.
-
|
All plugins cause this error now. Something must have happened between 12:00 UTC and now, because it was working fine for me before that. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, so on githubstatus.com it says that there's a partial outage for codespaces ("Degraded Codespace Experience", yeah it sure is), but it's labeled as beginning 30 minutes ago, so the timeline might not precisely fit |
Beta Was this translation helpful? Give feedback.
-
|
Are there any settings of the environment, maybe even synced, that could
affect this?
Are we just few exceptions here or is everyone experiencing this now? I
suppose it works for majority, what are we doing differently than the rest?
…On Thursday, March 12, 2026, Dark Blue Moon ***@***.***> wrote:
yeah somethign is wrong bruh , i need codespace for my project now this
error please do update me when it becomes normal
I'll try... I can't even do anything in Python without the plugin so,
until then, my current project is essentially useless.
—
Reply to this email directly, view it on GitHub
<#189290 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFT6PIAL7TBDP5ODVCPWYST4QK5FVAVCNFSM6AAAAACWPDSJIGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBZHAYTCMI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
AI Chat in codespaces does not seem to work for me any more. It still used to work few days ago but not today. It says it is not compatible any more (38.2) and offers the upgrade (to 39). But when I try to upgrade some error is returned.
Here is the paste of the log:
2026-03-12 02:56:20.591 [error] [Window] End of central directory record signature not found. Either not a zip file, or file is truncated.: Error: End of central directory record signature not found. Either not a zip file, or file is truncated.
at i_ (file:///vscode/bin/linux-x64/ce099c1ed25d9eb3076c11e4a280f3eb52b4fbeb/out/server-main.js:424:2620)
at file:///vscode/bin/linux-x64/ce099c1ed25d9eb3076c11e4a280f3eb52b4fbeb/out/server-main.js:424:3922
at /vscode/bin/linux-x64/ce099c1ed25d9eb3076c11e4a280f3eb52b4fbeb/node_modules/yauzl/index.js:40:7
at /vscode/bin/linux-x64/ce099c1ed25d9eb3076c11e4a280f3eb52b4fbeb/node_modules/yauzl/index.js:190:5
at /vscode/bin/linux-x64/ce099c1ed25d9eb3076c11e4a280f3eb52b4fbeb/node_modules/yauzl/index.js:712:5
at /vscode/bin/linux-x64/ce099c1ed25d9eb3076c11e4a280f3eb52b4fbeb/node_modules/yauzl/fd-slicer.js:33:7
at FSReqCallback.wrapper [as oncomplete] (node:fs:670:5)
What can I do to make the copilot chat for workspaces work again?
I tired creating a new codespaces environment, clicked to initialize the chat and got a response:
An error occurred while setting up chat. Would you like to try again?
End of central directory record signature not found. Either not a zip file, or file is truncated.
I am using web environment, nothing installed on my PC.
Beta Was this translation helpful? Give feedback.
All reactions