You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Pre-install VS Code extensions in desktop VS Code module #207
My appraoch it to Add an extra extensions parameter that accepts a list of extension IDs. Create a new run.sh script that uses code --install-extension to install each extension during VM provisioning after VS Code setup. Include basic error handling and ensure proper user context for persistent installations.
My appraoch it to Add an extra extensions parameter that accepts a list of extension IDs. Create a new run.sh script that uses code --install-extension to install each extension during VM provisioning after VS Code setup. Include basic error handling and ensure proper user context for persistent installations.
from what I understand installing extensions in a workspace where you aren't currently connected to it with said IDE, is difficult at least with code-cli to install the extensions during the workspace build.
Approach: Adds extensions, settings, and extensions_dir variables to the vscode-desktop module. On workspace start, a script installs the requested extensions to ~/.vscode-server/extensions/ and merges machine settings into ~/.vscode-server/data/Machine/settings.json.
This addresses the blocker from the previous attempt (#218): the script auto-detects an existing VS Code CLI and falls back to downloading VS Code Server when none is present, so it works on a fresh workspace. It follows the same per-module pattern already shipped in vscode-web and code-server, and exposes extensions_dir so the same approach can be reused by the Cursor/Windsurf/Kiro wrappers in follow-ups.
Activity
yashksaini-coder commentedon Jul 11, 2025
/attempt #207
My appraoch it to Add an extra extensions parameter that accepts a list of extension IDs. Create a new
run.shscript that usescode --install-extensionto install each extension during VM provisioning after VS Code setup. Include basic error handling and ensure proper user context for persistent installations.yashksaini-coder commentedon Jul 12, 2025
@matifali I have raised PR, for this issue, #218
matifali commentedon Jul 18, 2025
/bounty 100
8 remaining items
Pranith124 commentedon Aug 24, 2025
/attempt #207
m4rrypro commentedon Aug 25, 2025
/attempt 207
bpmct commentedon Sep 22, 2025
Hmm... Why is this challenging?
matifali commentedon Sep 22, 2025
Discussed internally, and we want to solve this more systematically for all IDEs based on VSCode.
DevelopmentCats commentedon Oct 22, 2025
from what I understand installing extensions in a workspace where you aren't currently connected to it with said IDE, is difficult at least with
code-clito install the extensions during the workspace build.this is described here in their documentation: https://code.visualstudio.com/docs/remote/ssh#_managing-extensions
DevelopmentCats commentedon Oct 22, 2025
Also this issue is relevant to this topic microsoft/vscode-remote-release#9454
lsrtech commentedon Jun 16, 2026
/attempt #207
I've submitted PR #926 to address this.
Approach: Adds
extensions,settings, andextensions_dirvariables to thevscode-desktopmodule. On workspace start, a script installs the requested extensions to~/.vscode-server/extensions/and merges machine settings into~/.vscode-server/data/Machine/settings.json.This addresses the blocker from the previous attempt (#218): the script auto-detects an existing VS Code CLI and falls back to downloading VS Code Server when none is present, so it works on a fresh workspace. It follows the same per-module pattern already shipped in
vscode-webandcode-server, and exposesextensions_dirso the same approach can be reused by the Cursor/Windsurf/Kiro wrappers in follow-ups.feat(vscode-desktop): pre-install remote extensions (#1094)
linear-code commentedon Sep 17, 2026
REG-116
feat(vscode-desktop): pre-apply machine settings (coder#207)