Journal / Web product development

VS Code extensions in 2026: what to keep, what to remove

Topics

  • Developer tools
  • VS Code
VS Code extensions in 2026: what to keep, what to remove

Most lists of the best VS Code extensions only tell you what to add. In 2026 the more useful question is what to take out. Keep the extensions that supply a language, a toolchain or a remote environment. Test the ones whose job VS Code now does itself. Remove anything deprecated, replaced or abandoned. Then split what is left into Profiles so each project loads only what it needs.

This is a documentation-based review, not a popularity ranking. Sources and install counts were checked on 11 November 2026; the scheduled publication date is 21 November 2026. Install counts come from the public Visual Studio Marketplace API and are cumulative downloads, not active users. A large number says an extension was installed often, not that it is good, current or safe.

What VS Code already does without an extension

Several well-known extensions exist because the editor once lacked a feature. For the items below I checked the release notes, the documentation or the source code of VS Code on 11 November 2026.

  • Bracket pair colorization. The editor setting editor.bracketPairColorization.enabled is on by default in the current source. The popular Bracket Pair Colorizer 2 is marked [Deprecated] on the Marketplace, and its author's notice says the idea "has become a native feature in VSCode". Remove it.
  • Settings sync. Settings Sync is built in. It syncs settings, installed extensions and their global enablement state across devices with a Microsoft or GitHub account. The old community extension of the same name was last updated in 2019.
  • Closing HTML tags. The built-in html.autoClosingTags setting is enabled by default. Check your JSX and Vue workflow before dropping a separate auto-close extension; I only confirmed the HTML setting.
  • Linked editing. The editor option editor.linkedEditing updates related symbols such as HTML tags while you type, depending on the language. It is off by default, so turn it on and test it before you uninstall Auto Rename Tag, whose last release was in February 2022.
  • Mermaid diagrams in Markdown. VS Code 1.121 merged Matt Bierner's Markdown Preview Mermaid Support into the editor as a built-in extension.
  • Dictation. From 1.131, dictation works without installing the VS Code Speech extension.
  • Sticky scroll and inlay hints. Sticky scroll is on by default. Inlay hints are on by default too, but the language extension (TypeScript, Rust and others) must supply the data, so they do not replace a language extension.

The biggest change is AI. Agent mode reached stable VS Code in 1.99 (March 2025), together with support for MCP server tools. 1.102 (July 2025) made MCP support generally available and open-sourced the Copilot Chat extension under the MIT licence. Since 1.116, Copilot Chat ships as a built-in extension, so a new install needs no extra extension for chat, inline suggestions or agents. If you want an assistant at all, the baseline is already in the editor. Third-party agents are now an additional choice, not a prerequisite.

A clean-up map for VS Code extensions: keep, built in now, remove, and check before installing.

Original diagram by Vlad Sedenko, licensed under CC BY 4.0. It is a decision map, not a product interface.

What was deprecated, replaced or left behind

GitHub Copilot and Copilot Chat are one extension now. The release notes describe it in three steps. In 1.106 the two extensions were consolidated and the Chat extension began serving inline suggestions. In 1.107 (10 December 2025) the original GitHub Copilot extension was disabled by default. In 1.109 it was deprecated and uninstalled automatically on update. The Marketplace still shows the old GitHub.copilot listing with about 74.9 million installs and a last update in October 2025. If you see it on a machine that has not updated, that is the leftover.

Docker became Container Tools. The Docker extension listing now describes itself as an extension pack. Its page says that Container Tools replaces the Docker extension, adds Podman support, and that the pack can be uninstalled while keeping Container Tools. Container Tools requires VS Code 1.109 or later.

IntelliCode is stale. The extension still has a public Marketplace page with about 62.7 million installs, but its last release is 1.3.2 from October 2024. I could not confirm in a primary source that Microsoft removed it from VS Code, so I do not claim that. The practical reading is narrower: it has not been updated for two years, and current AI-assisted completion comes from Copilot or another assistant. Check what it does for you and consider removing it.

Some AI extensions changed status. The Roo Code repository on GitHub is archived, with the last push on 15 May 2026, and its Marketplace page returns 404 on 11 November 2026. The Codeium listing (now "Windsurf Plugin") also returns 404, although it was last updated in August 2026. Both are flagged as unpublished in the Marketplace API. I found no statement explaining why, so I record only the observable facts: if you depend on either, do not expect to install it again from the Marketplace.

Stale does not always mean broken. REST Client (last update August 2022) and Git Graph (April 2021) still have many users. An old release date is a reason to look for a maintained alternative, not proof that the extension fails today.

Extensions by job

The table lists extensions I would evaluate by job. "Keep" means keep it if you do that work. "Consider" means a matter of taste, project or budget. "Check" means look before you rely on it. Counts are rounded and were read on 11 November 2026.

ExtensionJobInstallsVerdict
PythonPython language support244.9MKeep for Python work
PylancePython language server211.6MKeep for Python work
C/C++C and C++ tooling106.9MKeep for C and C++ work
PrettierFormatting72.9MKeep if the project uses it
ESLintLinting JavaScript and TypeScript53.8MKeep if the project has an ESLint config
RuffPython linting and formatting5.0MConsider for Python
BiomeJS/TS lint and format0.9MConsider as an alternative to the pair above
Tailwind CSS IntelliSenseTailwind class completion14.9MKeep for Tailwind projects
GitHub Pull RequestsPull requests in the editor37.4MKeep if you review there
GitLensGit history and blame53.9MConsider; its README advertises a Pro trial
Git GraphCommit graph15.7MConsider; last update April 2021
Dev ContainersContainerised dev environments42.7MKeep if you use them
Remote - SSHDevelop on a remote machine38.6MKeep if you use it
WSLDevelop in WSL on Windows41.3MKeep on Windows with WSL
Container ToolsContainers, Docker and Podman19.6MKeep; replaces the Docker extension
Error LensInline diagnostics10.3MConsider, a matter of taste
Material Icon ThemeFile icons36.2MOptional
Live ServerLocal reload for static pages84.3MConsider; Microsoft's Live Preview has 14.0M and carries a preview flag
Claude CodeAI coding agent30.0MConsider; one agent is enough
CodexAI coding agent16.6MConsider; compare with the one above
ClineAI coding agent5.9MConsider
ContinueAI coding agent4.5MConsider
Gemini Code AssistAI assistant5.7MCheck; rating 1.86 from 919 ratings
GitHub Copilot ChatAI assistant79.2MBuilt in since 1.116
GitHub CopilotOld inline suggestions74.9MRemove; deprecated
IntelliCodeOlder AI completions62.7MRemove after checking; last release October 2024
Bracket Pair Colorizer 2Bracket colours6.8MRemove; deprecated, native in the editor
Settings Sync (community)Settings sync4.3MRemove; use built-in sync
Auto Rename TagRename paired HTML tags26.2MTest linked editing first
Markdown Preview Mermaid SupportMermaid in Markdown5.5MRemove after updating to 1.121 or later
Thunder ClientHTTP client7.7MCheck; rating 2.35 from 776 ratings
REST ClientHTTP files7.7MConsider; last update August 2022

One rule keeps this list honest: if two extensions do the same job, keep one. In particular, run one AI coding agent as your daily driver. A second can be useful for comparison, but two assistants competing for the same completions and the same project instructions make it harder to tell which one caused a problem.

Ratings are a weak signal. A Marketplace score reflects only the people who chose to rate, and counts range from a few dozen to about a thousand reviews even for tools with tens of millions of installs. Use the rating together with the update date, the issue tracker and whether the publisher is verified, not on its own.

A minimal setup with Profiles

VS Code Profiles let you keep separate sets of settings, extensions, keyboard shortcuts, snippets, tasks and MCP servers. The documentation lists Profile Templates and an Empty Profile, which "includes no user customizations". That makes the clean-up practical, because you stop removing extensions from one global pile.

A small structure that works for most developers:

  1. Base profile. Only what you need everywhere: a theme or icon set you like, GitHub Pull Requests if you review in the editor, and one AI agent if you use one. In the Extensions view, Apply Extension to all Profiles makes an extension available in every profile.
  2. A profile per stack. One for the web with Prettier, ESLint and Tailwind, one for Python with Python, Pylance and Ruff, and so on. The documentation gives exactly this example: a JavaScript frontend profile and a Python backend profile, remembered per workspace.
  3. A reproduction profile. Create a profile from the Empty template. Per the documentation, an Empty Profile disables all extensions and modified settings, so you can see whether a problem comes from an extension, a setting or VS Code itself. Use it before blaming the editor.
  4. Workspace recommendations. A .vscode/extensions.json file lists extensions as publisher.extension so teammates are prompted to install the right ones.

Two limits are worth knowing. Settings Sync does not synchronise extensions to or from a remote window such as SSH, a dev container or WSL, so remote environments need their own list. And profiles reduce clutter, not risk: an extension in any profile still runs with the same permissions.

Before you install anything

The extension security documentation is blunt: the extension host has the same permissions as VS Code itself. Keep the checks short and routine.

  • Publisher. From 1.97, VS Code asks you to trust the publisher the first time you install from a third party. Treat the dialog as a decision. A blue check mark means the publisher proved domain ownership and has been in good standing for at least six months. It is a signal, not a guarantee.
  • Exact identifier. Compare the full publisher.extension ID with the project's own documentation. Look-alike names are a risk the Marketplace itself addresses: it says it stops authors from taking the names of official publishers and popular extensions, which is a narrower protection than checking every name.
  • Maintenance. Check the last update, the issue tracker and the repository link before relying on a tool.
  • Marketplace or Open VSX. The Marketplace terms of use say its offerings are intended for use only with Visual Studio, Visual Studio Code, GitHub Codespaces and Azure DevOps. Open VSX is a vendor-neutral open-source registry from the Eclipse Foundation that other editors use. The two catalogs do not contain exactly the same extensions, and their protections differ, so check where an extension comes from instead of assuming it is the same package.

That is deliberately brief. It covers the checks that fit into a few seconds. Marketplace protections such as malware scanning, publisher verification, a block list and signature checks reduce risk, but they do not remove it.

Cleaning up in practice

Start by listing what you have: the documented command code --list-extensions prints every installed extension, so read that output with this article beside it. Disable rather than uninstall the doubtful ones, work for a week, and uninstall what you did not miss. Re-enable one at a time if something breaks, so you learn which extension did the job.

If your team's setup has grown over the years and you want it simplified along with the build and review workflow, that is a normal part of web development work: agree on a shared extension list, a formatter and linter configuration, and recommended profiles, then keep them in the repository.

Sources

Primary sources read on 11 November 2026, before the scheduled publication date. Install counts and ratings are from the public Marketplace API on that date.