Troubleshooting

Start with the logs

Run Vegha: Show Logs to open the Vegha output channel. Engine start-up errors, protocol errors and send failures are logged there. If the engine stops responding, run Vegha: Restart Engine.

The Vegha view says there are no collections

A collection is a folder with a collection.bru file. Check that:

• you opened a folder or workspace, not a single file;
• the folder (or a subfolder) contains collection.bru;
• you’ve run Vegha: Refresh after creating or cloning files outside VS Code.

“Method not found” or “out-of-date engine”

The extension and its engine are released together. This message means you’re running an engine build that doesn’t match the extension, usually because vegha.sidecarPath points at an older build. Clear the setting to use the bundled engine.

The engine won’t start

• Make sure you installed the build for your platform. An Apple Silicon or Windows-on-Arm machine needs the arm64 package. The Marketplace picks the right one automatically, but a manually installed VSIX might not match.
• On Linux, the engine needs the usual .NET native dependencies (libicu isn’t required, but libssl and zlib are). Most desktop distributions have them.

OAuth 2.0 sign-in doesn’t come back

The authorization code flow redirects to a loopback address (http://127.0.0.1:<port>/…). Check that:

• the identity provider allows that redirect URI for your client;
• nothing blocks local loopback connections;
• in Remote/WSL/Codespaces windows, you opened the browser from VS Code, so the port is forwarded.

Variables show as unresolved

• Select an environment in the status bar.
• A value set by a script or capture only exists after that request has run in this session. Link the request with request chaining so it runs first.
• Vegha: Reset Session Variables clears stale runtime values.

An MCP agent can’t find Vegha

Re-run Vegha: Set Up MCP for Other Agents… and replace the old entry. The copied path changes with each extension version.

Reporting a bug

Open an issue at github.com/vegha-ai/Vegha/issues and include:

• the extension version (Extensions view) and your OS;
• the relevant lines from Vegha: Show Logs;
• a minimal .bru request that reproduces it, with secrets removed.