Settings
Open Settings (Ctrl+,) and search for Vegha, or edit settings.json directly.
vegha.dataDirectory
Section titled “vegha.dataDirectory”Default: empty (shared with the desktop app)
Where history, cookies and the secret-manager configuration live. Empty uses the Vegha desktop app’s data folder, so both see the same history and cookies. Set a path to keep the extension’s data separate.
vegha.openRequestsInVisualEditor
Section titled “vegha.openRequestsInVisualEditor”Default: true
Open requests from the Collections view in the visual request editor. Set to false to open
them as .bru text.
vegha.newUntitledOpensRequest
Section titled “vegha.newUntitledOpensRequest”Default: true
While the Vegha side bar is showing and a request is the active editor, a new untitled file (double-clicking the empty tab bar, or New File) opens an untitled GET request next to it instead of a blank text file.
vegha.codeLens.enabled
Section titled “vegha.codeLens.enabled”Default: true
Show Send and Open in Vegha Editor above requests in .bru text editors.
vegha.mcp.exposeInVSCode
Section titled “vegha.mcp.exposeInVSCode”Default: false
Also register Vegha’s MCP server with VS Code’s own MCP support, for agents that use it. Copilot already has the Vegha tools natively, so turning this on shows them twice there. For Claude Code, Cursor and others, use Vegha: Set Up MCP for Other Agents…. See MCP for other agents.
vegha.sidecarPath
Section titled “vegha.sidecarPath”Default: empty (the bundled engine)
Path to a vegha-sidecar executable, or a .dll run with vegha.dotnetPath. Use this only
to try a different engine build.
vegha.dotnetPath
Section titled “vegha.dotnetPath”Default: dotnet
The dotnet executable used when vegha.sidecarPath points at a .dll.
Opening every .bru file in the visual editor
Section titled “Opening every .bru file in the visual editor”This is a VS Code setting rather than a Vegha one:
"workbench.editorAssociations": { "*.bru": "vegha.requestEditor" }