DEV Community

Cover image for Copilot or Wakatime VSCode extensions not working on WSL: Solution
Pure
Pure

Posted on

2

Copilot or Wakatime VSCode extensions not working on WSL: Solution

TLDR: add

"remote.extensionKind": {
        "WakaTime.vscode-wakatime": [ "ui" ],
        "GitHub.copilot": [ "ui" ],
        "GitHub.copilot-chat": ["ui"]
}
Enter fullscreen mode Exit fullscreen mode

to your vscode settings.json

I recently encountered a problem with Windows' WSL. When opening a project from the WSL in Visual Studio Code, two of my extensions stopped working. Wakatime and Github Copilot. After a lot of debugging, it seems to be a web request certificate error that WSL makes. To fix this, simply run the extensions locally on Windows instead of on WSL by editing your VSCode settings.json (see TLDR).

ui stands for running the extension locally on Windows and workspace would mean running it on WSL.

There are also other solutions, such as ignoring the unauthorised requests or using a VPN or a proxy. But I think this is the easiest one.

Image of Timescale

🚀 pgai Vectorizer: SQLAlchemy and LiteLLM Make Vector Search Simple

We built pgai Vectorizer to simplify embedding management for AI applications—without needing a separate database or complex infrastructure. Since launch, developers have created over 3,000 vectorizers on Timescale Cloud, with many more self-hosted.

Read more

Top comments (0)

Postmark Image

Speedy emails, satisfied customers

Are delayed transactional emails costing you user satisfaction? Postmark delivers your emails almost instantly, keeping your customers happy and connected.

Sign up