v0.0.376 forgot the tree-sitter prebuilts?

[ctataryn-qh]

Describe the bug

I am getting errors when trying to execute bash commands that state:

Aborted(Error: ENOENT: no such file or directory, open '/path/to/home/.copilot/pkg/universal/0.0.376/tree-sitter.wasm'). Build with -sASSERTIONS for more info. 

Copying the tree-sitter*.wasm files from the 0.0.375 folder to the 0.0.376 folder fixed the issue.

Affected version

0.0.376

Steps to reproduce the behavior

1. Install the 0.0.376 version of copilot via npm
2. Run copilot and ask it a question that requires it to execute a bash command.
3. See that it reports an error along the lines described in the bug description above.

Expected behavior

No response

Additional context

Distributor ID: Ubuntu
Description:    Ubuntu 24.04.2 LTS
Release:        24.04
Codename:       noble

[devm33]

Checking the package tarball here: https://github.com/github/copilot-cli/releases/download/v0.0.376/github-copilot-0.0.376.tgz I see the tree-sitter wasm files. Maybe there was an error in downloading or extracting? If you have the ~/.copilot/logs/process-*.log when it did the auto-update would love to take a look

[ctataryn-qh]

@devm33 interesting. Here's the process log that has the first mention of 0.0.376

process-1767889218926-1764163.log

[devm33]

Thanks @ctataryn-qh, it looks like that one is after the update happened:

2026-01-08T16:20:24.051Z [INFO] No update needed, current version is 0.0.376, fetched latest release is v0.0.376

Do you have a log before that one? Maybe containing [INFO] Successfully downloaded package,

[ctataryn-qh]

@devm33 Interesting, I don't have a process*.log with that line, but I do have session*.log files with that line. The only issue being none that reference 376...

$ rg --sort=created 'downloaded' *.log

session-74907b18-0b87-44d8-9719-3048710a910d.log
15:2025-12-19T23:53:38.267Z [INFO] Successfully downloaded package, restart to update to version 0.0.372

session-b9a3fa1c-b345-4280-8abb-82bc536dec7a.log
15:2025-12-31T01:24:18.968Z [INFO] Successfully downloaded package, restart to update to version 0.0.373

session-3b5d86e3-8452-4303-ae34-9fd54311fc66.log
14:2026-01-05T17:30:34.835Z [INFO] Successfully downloaded package, restart to update to version 0.0.374

session-37728b74-a5a5-4ba7-9519-c45e6ecb5eae.log
16:2026-01-07T20:13:41.124Z [INFO] Successfully downloaded package, restart to update to version 0.0.375

That being said, even if I npm i -g @github/copilot that pkg folder does not have those .wasm files... Instead those files are in the folder /path/to/home/.copilot/pkg/linux-x64/0.0.376/tree-sitter.wasm (i.e. linux-x64 vs universal).

Solution: I managed to get it to work by uninstalling copilot using npm unintstall. Then manually removing that 0.0.376 folder under universal and reinstalling copilot using npm i

Question: is there perhaps logic in the search path for the .wasm files such that if it finds a folder with the current version under the universal folder it'll use that regardless if there is a more specific linux-x64 folder with the files present?

0.0.376 is the first version that I can see where there is an entry under the linux-x64 folder, all previous versions parked their files under the universal folder.

To add context: I run copilot both from command-line and in VSCode. Also, often times I have multiple copilot cli instances open.