devcode-extension

Install VS Code/Cursor extensions from a local .vsix via CLI (code, code-insiders, cursor, cursor-nightly). Use whenever asked to install an extension programmatically.

⭐3stars🔀0forks📁View on GitHub🕐Updated Jan 2, 2026

When & Why to Use This Skill

This Claude skill enables the programmatic installation of VS Code and Cursor extensions directly from local .vsix files via the command line. It streamlines development environment setup by supporting multiple IDE variants, including VS Code Insiders and Cursor Nightly, while providing options for isolated installations in CI/CD or sandbox environments.

Use Cases

  • Automated Workspace Configuration: Quickly set up new developer environments by batch-installing essential extensions from local backups without manual marketplace searches.
  • CI/CD Pipeline Integration: Automate the preparation of isolated testing environments for extension verification using specific user-data and extension directories.
  • Cross-IDE Management: Seamlessly manage and synchronize local extension installations across different versions of VS Code and Cursor (Stable and Nightly) using a unified CLI approach.
  • Air-gapped Environment Setup: Facilitate the installation of development tools in restricted or offline environments where direct access to the VS Code Marketplace is unavailable.
namedev.code-extension
descriptionInstall VS Code/Cursor extensions from a local .vsix via CLI (code, code-insiders, cursor, cursor-nightly). Use whenever asked to install an extension programmatically.
version1.0.0

dev.code-extension

Use this skill when the user asks to install a VS Code-compatible extension into VS Code or Cursor (stable or nightly).

Input contract

  • Expect a local filesystem path to a .vsix file.
  • If the user provides a Marketplace ID instead of a path, ask for the .vsix path (unless they explicitly want Marketplace install).

Install commands (local .vsix)

VS Code (stable)

code --install-extension "/path/to/extension.vsix" --force
code --list-extensions --show-versions

VS Code Insiders

code-insiders --install-extension "/path/to/extension.vsix" --force
code-insiders --list-extensions --show-versions

Cursor (stable)

cursor --install-extension "/path/to/extension.vsix" --force
cursor --list-extensions --show-versions

Cursor Nightly

Prefer cursor-nightly if it’s on PATH. If not (macOS default), call it from the app bundle:

"/Applications/Cursor Nightly.app/Contents/Resources/app/bin/cursor-nightly" --install-extension "/path/to/extension.vsix" --force
"/Applications/Cursor Nightly.app/Contents/Resources/app/bin/cursor-nightly" --list-extensions --show-versions

Verification

  • After install, verify by grepping the extension list:
    • cursor --list-extensions --show-versions | rg -n "<publisher>\\.<name>|<name>"

Automation/CI option (avoid touching a developer profile)

If the user wants isolated installs (recommended for scripts/CI), add:

  • --user-data-dir <dir>
  • --extensions-dir <dir>

Example:

cursor --user-data-dir /tmp/cursor-user --extensions-dir /tmp/cursor-ext --install-extension "/path/to/extension.vsix" --force

Sandbox note (Codex CLI)

Installing extensions writes to user/application support directories (outside the repo). In sandboxed runs, request escalated permissions for these commands.