Configure Vscode.prompt

---
description: "Apply baseline VS Code user-scope settings for fleet policy compliance"
lastReviewed: 2026-06-30
---

# Configure VS Code

Use this on first session setup (or when moving to a new machine) to apply a stable user-level VS Code policy.

For a first-session **orientation tour** (identity, what's loaded, where to start), use `/welcome` instead.
For WORKSPACE-scope settings + `.vscode/` assets (`markdown-light.css`, discovery-location keys), use `/configure-workspace`.

## Objective

Produce and apply a portable settings payload at user scope so every machine starts from the same safe defaults. Workspace settings remain the project-specific override layer and are handled by `/configure-workspace`.

## Source of truth

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

## Apply Steps

1. Load the baseline from `.github/config/welcome-baseline.json` (`settings` object).

2. Detect user settings path:
   - Windows: `%APPDATA%\Code\User\settings.json`
   - macOS: `~/Library/Application Support/Code/User/settings.json`
   - Linux: `~/.config/Code/User/settings.json`

3. Merge each baseline key/value into existing user settings (do not overwrite unrelated keys).

4. Verify applied keys by reading back values.

5. Report exactly which keys changed and which were already compliant.

## Reference Commands

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

### macOS / Linux (bash, zsh)