VS Code Extensions

how extensions work

Extensions install into ~/.vscode/extensions and run in a sandboxed process, separate from VS Code's own UI — a crashing extension shouldn't take the editor down with it. Browse and install from the Extensions view (ctrl+shift+x), or from the command line.

code --install-extension <publisher.extension-id> | https://code.visualstudio.com/docs/editor/extension-marketplace | installs an extension by id, without opening the GUI |'vsx_cli1'

code --list-extensions | | lists every extension currently installed |'vsx_cli2'

language support

Extension	What it adds
Python (ms-python.python)	the base Python extension — running, testing, environments
Pylance	the actual language server behind Python's autocomplete/type-checking; installs alongside Python
C/C++ (ms-vscode.cpptools)	IntelliSense and debugging for C/C++/CUDA source
Jupyter	run .ipynb notebooks directly inside VS Code

linting and formatting

Extension	What it adds
Black Formatter	auto-formats Python on save, no configuration debates
ESLint	lints JavaScript/TypeScript inline as you type
Prettier	opinionated auto-formatter for JS/TS/CSS/JSON/Markdown
Error Lens	shows lint errors inline at the end of the line, not just in the Problems panel

git tooling

VS Code's built-in Source Control view already covers day-to-day git — stage, commit, push, resolve conflicts. These extensions go further:

Extension	What it adds
GitLens	inline blame annotations, commit history per line, and a rich history explorer
Git Graph	a visual, interactive branch/commit graph — the GUI equivalent of `git log --graph`

remote and containers

These three are usually installed together as the "Remote Development" extension pack — the full treatment is in VS Code Remote Development.

Extension	What it adds
Remote - SSH	run VS Code's editing UI locally while everything executes on a remote machine over SSH
Dev Containers	develop inside a Docker container defined by the repo itself
WSL	the same remote-editing idea, targeting Windows Subsystem for Linux
Docker	manage images/containers from a side panel instead of the CLI

sharing extensions across a team

A repo can recommend its own extension list — VS Code prompts anyone who opens the folder to install them. This is the project-level equivalent of the personal Settings Sync feature (built in; sign in with a Microsoft or GitHub account to sync settings/extensions across your own machines).

ctrl+shift+p → Extensions: Configure Recommended Extensions (Workspace Folder) | | creates .vscode/extensions.json for the current repo |'vsx_team1'

reference

marketplace.visualstudio.com
code.visualstudio.com — extension marketplace