Connect Clawsmith to your coding agent. Ship products like crazy.Unlimited usage during betaGet API Key โ†’
โ† Back to dashboard
clawsmith.com/signal/vscode-local-user-workspace-settings
โš  IssueUnderserveddev_tool_cliLive

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.

Product Idea from this Signal

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 โ–ฒ

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.

vscodedeveloper-toolssettingsteam-workflowmonorepodx
Competitive163 leadsView Opportunity โ†’

Score Breakdown

GitHub
1,633

Gap Assessment

UnderservedExisting solutions leave gaps

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.