A VS Code extension that adds settings.json inheritance so one config file can extend another

VS Code has 1,692 reactions on an issue open since 2016 requesting that settings.json support an 'extends' key to inherit from a base config file, the same pattern used by tsconfig, eslint, and biome. The vendor closed it in 2018 citing 'use multi-root workspaces' then reopened it because that does not cover the inheritance use case at all. Today in 2026 the issue is still open with 157 comments. The painpoint is real for teams: shared editor rules (tab size, format-on-save, linting) need to live in one base file that every project's settings.json extends, without copy-pasting. No VS Code extension in the marketplace implements this. The product is a VS Code extension that reads an 'extends' key in settings.json, resolves the referenced base file (relative path or npm package), merges settings at activation time, and reloads when either file changes.