[Bug] Can't running copilot cli 1.0.49 on wsl after upgrade copilot

[robinsujob]

Describe the bug

wsl version: 6.6.114.1-microsoft-standard-WSL2

wsl-copliot.mp4

looks like stuck..??

Affected version

copilot --version GitHub Copilot CLI 1.0.49.

Steps to reproduce the behavior

No response

Expected behavior

No response

Additional context

No response

[t-palanis]

seeing the same error on latest update in wsl2

[t-palanis]

I tried the workaround suggested in this thread #1199 to start copilot in --no-auto-update but still stuck on same screen "loading envt..."

[AlexiaChen]

same, when upgrade to 1.0.49 on WSL2, the whole of CLI stuck, cannot accept any input and very very slow

[AlexiaChen]

I tried the workaround suggested in this thread #1199 to start copilot in --no-auto-update but still stuck on same screen "loading envt..."

cannot revert ,

[chrisphamboost]

It’s so slow—I have to wait a long time before I can start the prompt

[sfortier-sjsr]

The new version is completely unusable. Reverted to previous version and it works like before.

[TangLongbin]

The new version is completely unusable. Reverted to previous version and it works like before.

How can I downgrade my copilot cli to previous version? I tried update command and reinstalling with VERSION="v1.0.48", but copilot --version still show v1.0.49.

[TangLongbin]

The new version is completely unusable. Reverted to previous version and it works like before.

How can I downgrade my copilot cli to previous version? I tried update command and reinstalling with VERSION="v1.0.48", but copilot --version still show v1.0.49.

Copilot CLI downgrade fix

If Copilot keeps jumping back to a newer version after reinstall, it's usually the runtime cache, not npm.

npm uninstall -g @github/copilot
npm install -g @github/copilot@1.0.48 --force

rm -rf ~/.cache/copilot*
rm -rf ~/.config/copilot*
rm -rf ~/.local/share/copilot*

copilot --version
which copilot

Optional (helps avoid auto-upgrade in some cases):

echo 'export COPILOT_AUTO_UPDATE=false' >> ~/.zshrc
source ~/.zshrc

[robinsujob]

The new version is completely unusable. Reverted to previous version and it works like before.

How can I downgrade my copilot cli to previous version? I tried update command and reinstalling with VERSION="v1.0.48", but copilot --version still show v1.0.49.

Copilot CLI downgrade fix

If Copilot keeps jumping back to a newer version after reinstall, it's usually the runtime cache, not npm.

npm uninstall -g @github/copilot
npm install -g @github/copilot@1.0.48 --force

rm -rf ~/.cache/copilot*
rm -rf ~/.config/copilot*
rm -rf ~/.local/share/copilot*

copilot --version
which copilot
Optional (helps avoid auto-upgrade in some cases):

echo 'export COPILOT_AUTO_UPDATE=false' >> ~/.zshrc
source ~/.zshrc

same issue: #1948

[TangLongbin]

The new version is completely unusable. Reverted to previous version and it works like before.

How can I downgrade my copilot cli to previous version? I tried update command and reinstalling with VERSION="v1.0.48", but copilot --version still show v1.0.49.

Copilot CLI downgrade fix

If Copilot keeps jumping back to a newer version after reinstall, it's usually the runtime cache, not npm.

npm uninstall -g @github/copilot
npm install -g @github/copilot@1.0.48 --force

rm -rf ~/.cache/copilot*
rm -rf ~/.config/copilot*
rm -rf ~/.local/share/copilot*

copilot --version
which copilot
Optional (helps avoid auto-upgrade in some cases):

echo 'export COPILOT_AUTO_UPDATE=false' >> ~/.zshrc
source ~/.zshrc

same issue: #1948

Because your copilot is not installed via npm. You need to remove the copilot binary in .local/bin. Make sure which copilot shows a npm binary.