Configure Vscode Verify.prompt

---
description: "Read-only audit of user-level VS Code/Copilot settings compliance"
lastReviewed: 2026-06-30
---

# Configure VS Code — Verify

Use this to verify fleet policy compliance on a machine without changing any settings.

For a WORKSPACE-scope audit (`.vscode/` assets, discovery-location keys), use `/configure-workspace-verify`.

## Objective

Audit user-scope VS Code settings against the central baseline and report drift. Project-specific overrides belong in workspace `.vscode/settings.json` and are audited by `/configure-workspace-verify`.

## Source of truth

The baseline lives in `.github/config/welcome-baseline.json` (`settings` object). Both `/configure-vscode` (apply) and `/configure-vscode-verify` (this audit) load from the same file — update once.

## Read-Only Steps

1. Load the baseline from `.github/config/welcome-baseline.json` (`settings` object).
2. Resolve the user settings path for the current OS:
   - Windows: `%APPDATA%\Code\User\settings.json`
   - macOS: `~/Library/Application Support/Code/User/settings.json`
   - Linux: `~/.config/Code/User/settings.json`
3. Read `settings.json` as-is.
4. Compare each baseline key/value pair.
5. Classify each key:
   - `compliant` (value matches)
   - `drift` (key exists but value differs)
   - `missing` (key absent)
6. Report compliance summary and drift table.
7. Recommend running `/configure-vscode` only if drift or missing keys are found.

## Reference Commands (read-only audit)

Three shells, one payload. Pick the one for your OS.

### macOS / Linux (bash, zsh)