Settings

Open Settings with Ctrl+, (Cmd+, on Mac), the ⚙ button, or File ▸ Preferences. The Settings tool and the settings.json files are always in sync: change one and the other follows. You can also change any setting from the command palette by typing its name.

built-in defaults  →  User settings  →  Workspace settings
                     (your browser)     (.codevre/settings.json in the project)

The later layer wins, key by key. A Workspace file only overrides the keys it contains. Object settings such as files.exclude are merged entry by entry, so a Workspace files.exclude adds to your User one instead of replacing it.

With no project open, only User settings apply. When you close a project or open another, its Workspace settings are dropped, so one project's vre.settings.root never leaks into the next.

Your settings for every project: theme, font size, layout preferences and so on.

• Stored in this browser's local storage (key codevre-user-settings).
• Other open Codevre tabs follow changes immediately.
• Preferences ▸ User Settings opens them. Reset All in the Settings tool restores the defaults, with Undo.

Settings for one project, stored in the project and saved with it:

1. .codevre/settings.json, or if that doesn't exist,
2. .vscode/settings.json.

Only the first one found is used; they aren't merged with each other. The format is JSONC: comments and trailing commas are fine. If you save a file with a syntax error, the last valid settings stay in effect until you fix it.

Open it with Preferences ▸ Open Workspace settings.json, or right-click the .codevre folder and choose Create settings.json.

{
  // Workspace settings for this project. They override your User settings,
  // key by key.
  "vre.preview.autoRun": true,
  "vre.settings.root": "",
  "vre.settings.Wait": 100,
  "vre.settings.ignoreFiles": []
}

Codevre reads Live Server's keys as aliases, so a project from VS Code works unchanged:

If both are set, the vre.* key wins.

Project settings in User settings follow you into every other project and can break them. For example, vre.settings.root: "public" empties the preview of any project without a public folder. When the Agent changes a setting, vre.*, liveServer.* and files.exclude always go to the Workspace file.

When a change could go either way, some commands (such as Color Theme) write to the Workspace file only if the project already sets that key, and to User settings otherwise.

See localhost:codevre.

Any Monaco option, as editor.<option> (one level of nesting, like editor.minimap.enabled).

All AI settings are User only. Keys aren't settings; they're saved to your Codevre account and never written to settings.json.

Some Agent preferences, such as Chat/Agent mode, approvals, reasoning effort and recent models, are kept per browser rather than as settings. See Agent settings.

This is a summary. See Settings reference for every setting, including the cursor, suggestions, minimap and breadcrumbs.

• User / Workspace tabs. The active tab decides where a change is written. The Workspace tab is read-only with no project open, or while settings.json has a syntax error; a banner shows the line and column and an Open settings.json button.
• Search matches keys, titles, descriptions and values ("N Settings Found"). Ctrl+F focuses it; Esc clears it.
• Modified settings are marked. "(Also modified in: Workspace)" links to the other tab. The filter button shows modified settings only.
• Setting a value equal to the inherited one removes the key instead of writing a duplicate.
• Each setting's ⋯ menu (or right-click) has Reset Setting, Apply to This Project / Apply to All Projects, Copy Setting ID, Copy Setting as JSON and Edit in settings.json.
• The header ⋯ menu has Reset All User Settings… and Reset All Workspace Settings…, both with Undo for 8 seconds, plus Open Workspace settings.json.
• Changing a Workspace setting edits settings.json in place, keeping your comments, key order and formatting. If the project has no settings file, the first change creates .codevre/settings.json.
• Keys the editor doesn't know are listed under Other with their value.
• Project › Project Settings holds the project's name, description, tags, cover image, visibility and link. See Files and projects.

The Settings tool lists every setting with its description. Use its search box, or ask the Agent to list_settings.