How to Install VSCodium on Debian 13, 12 and 11

Debian does not ship VSCodium from its default package archive, so the package source you choose matters before the first install command. VSCodium gives Debian users the familiar Visual Studio Code editing workflow without Microsoft’s telemetry, branding, or default Marketplace wiring, while still providing the codium launcher, desktop menu entry, integrated terminal, debugging UI, and extension support expected from a VS Code-style editor.

The recommended path is the current upstream APT repository at repo.vscodium.dev, because Debian keeps updates inside normal package management once the source is configured. Flatpak remains useful when you prefer Flathub-managed desktop apps, and Extrepo is covered for administrators who already standardize third-party APT sources through Debian’s Extrepo tooling. The commands apply to Debian 13 (Trixie), Debian 12 (Bookworm), and Debian 11 (Bullseye) on standard amd64 systems, with the upstream repository also advertising arm64 and armhf packages.

Install VSCodium on Debian

Choose a VSCodium Installation Method

Most Debian desktop users should use the official APT repository. It installs the codium package, creates the codium command, adds the desktop launcher, and lets future releases arrive through apt upgrade. Choose Flatpak only when you deliberately want the Flathub package. Choose Extrepo only when you already manage third-party repositories with Extrepo and understand that it creates a separate VSCodium source file.

Method	Source or Channel	Update Behavior	Best For	Trade-offs
Official APT repository	VSCodium repository	Updates through APT	Most Debian desktop users who want the normal codium package	Adds a third-party APT source and signing key that you must remove during cleanup
Flatpak	Flathub	Updates through Flatpak	Users who prefer Flathub packaging or do not want another APT source	Uses the Flatpak app ID com.vscodium.codium and can require filesystem permission adjustments
Extrepo	Debian Extrepo data	Updates through APT after Extrepo enables the source	Administrators already using Extrepo for third-party repository tracking	Must not be enabled beside the official source because both expose the same codium package

Use only one VSCodium package source at a time. Configuring both the official repository and Extrepo can leave APT with duplicate VSCodium entries, different Signed-By paths, or confusing package-source output.

VSCodium also publishes direct .deb files through its repository package listing and GitHub releases, but the repository method is better for normal Debian desktops because it keeps update and removal ownership inside APT. A direct package download makes sense mainly for offline transfer or a temporary test system, and that workflow needs separate download, integrity, update, and cleanup steps.

Prepare Debian for the VSCodium Repository

Refresh APT and install the small tools needed for HTTPS repository access and key handling. Minimal Debian installations may not already include curl, gpg, or current CA certificates.

sudo apt update
sudo apt install ca-certificates curl gpg

These commands use sudo because APT sources, keyrings, and package transactions require root privileges. If your account cannot run sudo, configure sudo access first with the Debian sudoers setup guide.

The curl command downloads the repository key and source file. If you want a deeper refresher on options such as -f, -s, -S, and -L, see the curl command guide.

Add the VSCodium Signing Key

Download the current VSCodium repository key and store it as a binary keyring under /usr/share/keyrings. This keeps the key scoped to the VSCodium source through the source file’s Signed-by field instead of placing it in APT’s global trust store.

curl -fsSL https://repo.vscodium.dev/vscodium.gpg | sudo gpg --dearmor --yes -o /usr/share/keyrings/vscodium.gpg

The saved keyring is separate from older VSCodium examples that used apt-key, /etc/apt/trusted.gpg.d/, or the older vscodium-archive-keyring.gpg filename. Avoid mixing those older files with the current source unless you are intentionally cleaning up a previous installation.

Add the VSCodium DEB822 Source File

Download the upstream DEB822 source file directly into /etc/apt/sources.list.d/. The file uses the codename-neutral vscodium suite, so you do not need to substitute trixie, bookworm, or bullseye into the source entry.

sudo curl -fsSLo /etc/apt/sources.list.d/vscodium.sources https://repo.vscodium.dev/vscodium.sources

Inspect the file once before refreshing APT. This is also a useful way to confirm the keyring path and supported architectures if you are working from a minimal or non-amd64 Debian installation.

sed -n '1,8p' /etc/apt/sources.list.d/vscodium.sources

Types: deb
URIs: https://repo.vscodium.dev/deb
Suites: vscodium
Components: main
Architectures: amd64 arm64 armhf
Signed-by: /usr/share/keyrings/vscodium.gpg

Debian 13 commonly uses DEB822 .sources files already, while upgraded Debian 12 and Debian 11 systems may still have legacy .list files for other repositories. APT can read this VSCodium .sources file on the Debian releases covered here, and keeping the repository in DEB822 format makes later cleanup easier to audit. The VSCodium repository page also offers vscodium.list for older Debian-family setups; do not add that file when using the .sources workflow here.

Refresh APT and Verify the VSCodium Package

Refresh APT so Debian reads the new repository metadata.

sudo apt update

Confirm that APT now sees codium from repo.vscodium.dev. This step matters because a successful source-file download does not prove the package is visible to APT.

apt-cache policy codium

codium:
  Installed: (none)
  Candidate: 1.116.02821
  Version table:
     1.116.02821 500
        500 https://repo.vscodium.dev/deb vscodium/main amd64 Packages

The version number changes as VSCodium releases new builds. The important parts are that Candidate is not (none) and the repository line points to https://repo.vscodium.dev/deb. On arm64 or armhf systems, the architecture label in the package line should match your system architecture.

Install the Codium Package

Install VSCodium from the repository. The Debian package name is codium, not vscodium, and the terminal launcher uses the same codium name.

sudo apt install codium

The package installs the application payload under /usr/share/codium, creates a desktop launcher named codium.desktop, and makes the codium command available in the normal system path. Current Debian installs may also pull socat as a dependency; apt autoremove can remove it later if no other package needs it.

Verify the VSCodium Installation

Check the installed package state first.

dpkg-query -W -f='${db:Status-Abbrev} ${binary:Package} ${Version} ${Architecture}\n' codium

ii  codium 1.116.02821 amd64

Then confirm the command launches far enough to print its version data.

codium --version

1.116.02821
221e0a382c0be3a673a4e4cab0601344a0b3de3a
x64

The first line is the VSCodium version, the second line is the build commit, and the third line is the runtime architecture label. Your values will change as the upstream repository publishes newer builds.

Install VSCodium with Flatpak on Debian

Flatpak is a good alternative when your Debian desktop already uses Flathub or when you prefer app updates to stay outside APT. The Flathub package uses the app ID com.vscodium.codium and is published separately from the APT repository package.

If Flatpak and Flathub are not configured yet, complete the Flatpak setup on Debian first. After Flathub is enabled, install VSCodium with:

flatpak install flathub com.vscodium.codium

Verify the installed Flatpak metadata:

flatpak info com.vscodium.codium

Launch the Flatpak build from a terminal with:

flatpak run com.vscodium.codium

Flatpak permissions can affect project folders outside your home directory, external drives, SSH agent access, and development tool integrations. Use Flatseal or a focused flatpak override only for the directories or sockets your workflow actually needs.

For example, grant the Flatpak package access to a project directory stored outside your home folder with:

flatpak override --user --filesystem=/path/to/project com.vscodium.codium

Replace /path/to/project with the real directory. Avoid broad filesystem overrides unless you understand the trade-off, because they reduce the benefit of using Flatpak packaging in the first place.

Use Extrepo for VSCodium on Debian

Extrepo is not the default recommendation for a refreshed VSCodium install because the upstream repository now publishes a current key and source file directly. Extrepo remains useful if you already use Debian’s curated Extrepo metadata and want VSCodium managed through the same workflow as your other third-party repositories.

Install Extrepo from Debian’s own repository:

sudo apt update
sudo apt install extrepo

Search the packaged Extrepo data before enabling the source. This confirms the repository definition on your installed Debian release.

extrepo search vscodium

Found vscodium:
---
description: VS Codium repository - FLOSS binaries of VS code.
source:
  Architectures: amd64 arm64
  Components: main
  Suites: vscodium
  Types: deb
  URIs: https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/

Enable the repository only if you are not using the official /etc/apt/sources.list.d/vscodium.sources file from the earlier method.

sudo extrepo enable vscodium
sudo apt update
sudo apt install codium

Extrepo creates a source file named /etc/apt/sources.list.d/extrepo_vscodium.sources and stores its key material under /var/lib/extrepo/keys/. For broader Extrepo usage and repository hygiene, see manage third-party APT repositories on Debian with Extrepo.

Launch and Get Started with VSCodium on Debian

Start VSCodium from the Desktop or Terminal

APT and Extrepo installations add a normal desktop launcher. On GNOME, open Activities, search for VSCodium, and start the editor from the application grid. Other Debian desktop environments usually place it in the Development or Programming menu.

From a terminal, start the APT or Extrepo version with:

codium

For the Flatpak version, use the Flatpak app ID instead:

flatpak run com.vscodium.codium

Open a Project Folder

A common first workflow is to open a project directory rather than starting with an empty window. Create a small workspace and open it with the APT-installed launcher:

mkdir -p ~/Projects/vscodium-demo
printf '# VSCodium on Debian\n' > ~/Projects/vscodium-demo/README.md
codium ~/Projects/vscodium-demo

Inside VSCodium, the Explorer should show README.md. This confirms that the editor can open a normal user-owned project folder, which is the safest starting point before editing root-owned files or system configuration.

If you installed the Flatpak build, open the same folder with:

flatpak run com.vscodium.codium ~/Projects/vscodium-demo

Avoid Running VSCodium as Root

Use VSCodium as your normal user account. Starting a graphical editor with sudo codium can create root-owned files inside your profile, confuse extension permissions, and make later launches fail in ways that look like application bugs. For files under /etc or other root-owned paths, edit a user-owned copy, use a terminal editor with sudo, or apply the privileged change from the integrated terminal after reviewing the diff.

Use Git Projects in VSCodium

VSCodium can display Git changes in the Source Control view, but it still relies on the system git command for normal repository work. Install Git first if your Debian desktop does not already have it.

sudo apt install git
git --version

For a fuller Git setup, including identity configuration and common commands, use the Git on Debian installation guide.

Understand Extensions and Open VSX

VSCodium uses the Open VSX Registry by default instead of Microsoft’s Visual Studio Marketplace. Many common extensions are available, but some Microsoft-published or Marketplace-restricted extensions are limited to official Visual Studio Code builds. That difference is one of the biggest practical changes for Debian users moving from VS Code to VSCodium.

Use the Extensions view inside VSCodium for normal installs. If a specific extension is missing, check whether the publisher distributes it through Open VSX, whether an open alternative exists, or whether the extension license restricts it to Microsoft’s builds. The upstream VSCodium extension documentation explains the Marketplace difference and known workarounds.

Keep VSCodium Separate from VS Code

VSCodium and Visual Studio Code can coexist on the same Debian desktop. VSCodium uses the codium command and stores settings under ~/.config/VSCodium, while Microsoft’s VS Code package uses the code command and ~/.config/Code. Extensions are separate as well.

command -v codium
command -v code

If both commands return paths, both editors are installed. Choose the editor you want explicitly from the terminal, desktop menu, or file association settings instead of assuming one replaced the other.

Update VSCodium on Debian

APT and Extrepo installations update through APT because both methods expose the codium package to Debian’s package manager. Use a normal system upgrade to include VSCodium with the rest of your desktop packages:

sudo apt update
sudo apt upgrade

To check only VSCodium without upgrading the whole system, use:

sudo apt update
sudo apt install --only-upgrade codium

If APT reports that codium is already the newest version, the package manager checked the configured repository and found no newer build for your system.

Flatpak installations update through Flatpak instead:

flatpak update com.vscodium.codium

Remove VSCodium from Debian

Remove the Official APT Repository Installation

Purge the codium package first. This removes the application package and any package-level configuration, but it does not delete your per-user editor profile.

sudo apt purge codium

Remove the repository source and keyring created by the official APT method.

sudo rm -f /etc/apt/sources.list.d/vscodium.sources
sudo rm -f /usr/share/keyrings/vscodium.gpg
sudo apt update

Confirm that APT no longer has a repository candidate for codium:

apt-cache policy codium

No candidate output means the active VSCodium source is gone. If APT still shows a candidate, another source file is still configured.

Remove dependencies that APT marks as no longer required. Review the package list before confirming, because apt autoremove can include older orphaned packages unrelated to VSCodium.

sudo apt autoremove

Remove the Extrepo Installation

If you used Extrepo, purge the editor package and disable the Extrepo-managed source.

sudo apt purge codium
sudo extrepo disable vscodium
sudo rm -f /etc/apt/sources.list.d/extrepo_vscodium.sources
sudo rm -f /var/lib/extrepo/keys/vscodium.asc
sudo apt update

Keep the extrepo package installed if you use it for other repositories. Remove Extrepo itself only when VSCodium was the only reason you installed it.

sudo apt purge extrepo
sudo apt autoremove

Remove the Flatpak Installation

Remove the Flathub package with its app ID.

flatpak uninstall com.vscodium.codium

Remove unused Flatpak runtimes only after Flatpak shows that they are no longer needed by other apps.

flatpak uninstall --unused

Remove VSCodium User Data

Package removal does not delete your settings, extensions, workspaces, or cache. Remove these directories only when you no longer need your VSCodium profile.

The next commands permanently delete VSCodium settings, installed extensions, local workspace state, and cached files. Back up anything you want to keep before running them; Timeshift on Debian can help with broader desktop rollback planning, but a manual copy of the profile directories is often enough for editor settings.

For APT or Extrepo installations, remove the normal VSCodium profile, extension, and cache directories:

rm -rf ~/.config/VSCodium
rm -rf ~/.vscode-oss
rm -rf ~/.cache/VSCodium

For Flatpak installations, remove the Flatpak app data directory:

rm -rf ~/.var/app/com.vscodium.codium

Troubleshoot VSCodium on Debian

APT Cannot Locate the Codium Package

Unable to locate package codium usually means APT has not read the VSCodium source or the source file was not created where APT expects it. Check the source file and package policy before repeating the install command.

ls -l /etc/apt/sources.list.d/vscodium.sources
sudo apt update
apt-cache policy codium

If the file is missing, repeat the official repository setup. If the file exists but apt update fails, fix the error from APT before installing; package installation cannot succeed until the metadata refresh works.

APT Reports a VSCodium Signature or Key Error

Signature errors can happen when an old keyring path remains from a previous VSCodium setup, when the key download failed, or when APT is reading two VSCodium source files with different Signed-By values. Reinstall the current key first.

curl -fsSL https://repo.vscodium.dev/vscodium.gpg | sudo gpg --dearmor --yes -o /usr/share/keyrings/vscodium.gpg
sudo apt update

If the error continues, find all VSCodium-related source entries.

grep -R -E "vscodium|paulcarroty" /etc/apt/sources.list /etc/apt/sources.list.d 2>/dev/null

Keep either the official /etc/apt/sources.list.d/vscodium.sources file or the Extrepo file, not both. Remove stale VSCodium source files and old keyrings that no remaining source references.

sudo rm -f /etc/apt/sources.list.d/extrepo_vscodium.sources
sudo rm -f /usr/share/keyrings/vscodium-archive-keyring.gpg
sudo rm -f /var/lib/extrepo/keys/vscodium.asc
sudo apt update

Do not remove /etc/apt/sources.list.d/vscodium.sources or /usr/share/keyrings/vscodium.gpg if you are keeping the official repository method.

Flatpak VSCodium Cannot Open a Project Folder

The Flatpak build may not see project directories outside its allowed filesystem locations. Check the exact path and grant only the project directory you need.

flatpak override --user --filesystem=/path/to/project com.vscodium.codium

After changing permissions, close and reopen the Flatpak app. If the project is on a removable drive, confirm the drive is mounted before launching VSCodium.

The Extension Search Shows No Results

VSCodium searches Open VSX by default. If the Extensions view is empty, first confirm that the registry site is reachable from your Debian session.

curl -I https://open-vsx.org/

HTTP/2 200
content-type: text/html

A successful HTTP response means the site is reachable. If a specific extension is still missing, it may not be published to Open VSX or may be restricted to Microsoft’s Marketplace. Check the extension publisher’s page and the VSCodium extension documentation before changing VSCodium’s product settings.

VSCodium Fails to Start on the Desktop

Start with the package source and command path rather than disabling security features. The current Debian APT package exposes /usr/bin/codium, installs its application files under /usr/share/codium, and does not normally add a Codium-specific AppArmor profile.

command -v codium
dpkg-query -W -f='${db:Status-Abbrev} ${binary:Package} ${Version}\n' codium
apt-cache policy codium

If the package and command are present but the graphical window does not appear, launch it from a terminal and read the error text. Only investigate AppArmor if kernel logs show fresh denials tied to codium; a generic launch failure is more often a display session, extension, GPU, permissions, or Flatpak access issue.

sudo journalctl -k --no-pager | grep -i apparmor | grep -i codium

A matching denial deserves targeted troubleshooting. An empty result means AppArmor is not the visible blocker, so avoid broad AppArmor changes.

Related Debian Developer Guides

After VSCodium is installed, the next useful setup depends on your development workflow. Install Docker on Debian for containerized projects, use GitHub Desktop on Debian if you prefer a visual Git client, or install PyCharm on Debian when you need a Python-focused IDE alongside VSCodium.

Conclusion

VSCodium is installed on Debian with a verified package source, a working codium command, and a clear update path through either APT or Flatpak. Keep the official repository as the default for normal desktop use, use Extrepo only when it fits your existing repository workflow, and check Open VSX early when extension behavior differs from Microsoft’s VS Code builds.