A VS Code extension that layers a gitignored user-local settings file on top of shared workspace settings
VS Code has 1,429 reactions on a 2017 issue requesting a .vscode/settings.local.json file that is gitignored and layered on top of the shared .vscode/settings.json. This lets a team commit shared project settings like tab size and format-on-save while each developer keeps personal overrides like font size, debug paths, and git.autofetch local to their machine without touching the shared file. The vendor's repeated answer is 'use multi-root workspaces' which adds significant folder structure complexity and does not work for single-folder projects. A partial extension (Workspace Config+) has 19K installs but handles a different case (applying settings to nested folders) and does not implement gitignored user-local override layering. The issue received a comment as recently as June 2026 with 204 total comments. The product is a VS Code extension that loads .vscode/settings.local.json at workspace activation, deep-merges it over the shared settings, and writes a .gitignore entry for the file on first use.
A CLI tool and editor extension that adds settings inheritance, per-workspace extension enablement, and a gitignored personal override layer to VS Code
5.1k โฒScore Breakdown
Social Proof 1 sources
Gap Assessment
Vendor defers to multi-root workaround that does not work for single-folder projects. Partial competitor (Workspace Config+, 19K installs) solves a different sub-case. Core user-local gitignored settings layer is unshipped. Open slot.