# VSCodium

## Extensions not loading in VSCodium

1. Find your binary location: `which codium`
2. Navigate to that directory and search for a file called `product.json` which should be in `./resources/app/` relative to the root of the application directory (the binary should be in `./bin`)
3. Search for `"extensionsGallery"` and replace the URLs as follows:

```
"extensionsGallery": {
    "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
    "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
    "itemUrl": "https://marketplace.visualstudio.com/items"
}
```

## 429 Too Many Requests on Ubuntu/Debian-based systems in VSCodium

Add the GPG key:

```
wget -qO - https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/raw/master/pub.gpg | gpg --dearmor | sudo dd of=/etc/apt/trusted.gpg.d/vscodium-archive-keyring.gpg;
```

Change `/etc/apt/sources.list.d/vscodium.list` to:

```
deb [signed-by=/etc/apt/trusted.gpg.d/vscodium-archive-keyring.gpg] https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/ vscodium main
```

Update and upgrade:

```
sudo apt update;
sudo apt upgrade;
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://notes.joeir.net/software-development/vscodium.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.