A CLI tool and editor extension that adds settings inheritance, per-workspace extension enablement, and a gitignored personal override layer to VS Code

VS Code offers user settings and workspace settings but no way to layer them: teams cannot share a base config that individuals extend locally, and there is no committable file to declare which extensions are enabled or disabled per workspace. Three GitHub issues spanning 8-9 years (15909, 40233, 40239) with a combined 5070 reactions show developers want an extends-style inheritance for settings.json, a .vscode/settings.local.json that is gitignored by default for personal overrides, and a .vscode/extensions-enabled.json that is committed to the repo so extension activation state is reproducible across machines. The extension ships a small CLI companion for scaffolding the config tree in monorepos.

Demand Breakdown

GitHub

5,070

Social Proof 3 sources

Add ability to extend from other settings files

@maxdeviant · 2016-11-22

1,849 GH

[Feature] Local Workspace settings

@firelizzard18 · 2017-12-14

1,633 GH

Feature Request: Enable/disable extensions from config file

@michaeljota · 2017-12-15

1,588

Gap Assessment

CompetitiveMultiple tools exist but differentiation opportunities remain

3 tools exist (Tabaqa, VS Code Profiles (native), EditorConfig) but gaps remain: Requires a new sidecar file instead of extending the native .vscode/settings.json; does not handle per-workspace extension enable/disable in a committed file; does not provide a gitignored personal override layer out of the box; low adoption and no CLI companion for monorepo scaffolding.; Profiles are per-user and not shared at the workspace/repo level; no inheritance or layering between profiles; cannot commit a profile to a repo so all teammates inherit it..

Features7 agent-ready prompts

Settings inheritance via extends in .vscode/settings.json

▶

Gitignore-safe personal local override layer (.vscode/settings.local.json)

▶

Committable per-workspace extension enable/disable config (.vscode/extensions-enabled.json)

▶

Monorepo settings tree scaffolding CLI

▶

Settings diff and conflict visualization panel

▶

Team settings template library and one-click import

▶

CI/CD settings consistency gate

▶

Competitive LandscapeFREE

Product	Does	Missing
Tabaqa	Adds an extends field to a separate tabaqa.json sidecar file that merges settings from other files or URLs up the folder tree.	Requires a new sidecar file instead of extending the native .vscode/settings.json; does not handle per-workspace extension enable/disable in a committed file; does not provide a gitignored personal override layer out of the box; low adoption and no CLI companion for monorepo scaffolding.
VS Code Profiles (native)	Lets users create named profiles with their own settings, extensions, and keybindings.	Profiles are per-user and not shared at the workspace/repo level; no inheritance or layering between profiles; cannot commit a profile to a repo so all teammates inherit it.
EditorConfig	Provides a .editorconfig file that propagates a small set of formatting settings (indent style, line endings, charset) up the directory tree.	Covers only a handful of editor-agnostic formatting settings; has no concept of VS Code-specific settings, extension activation, or personal local overrides.