Skip to content
Vegha VS Code

Data & privacy

Vegha sends nothing anywhere except the requests you send and the auth flows you start. There are no analytics, crash reports or update checks from the extension itself. VS Code’s own telemetry settings are separate and don’t affect Vegha.

DataWhere
Collections, requests, environments.bru / .env.json files in your workspace.
Secret variable values in .env.json environmentsThe encrypted store shared with the desktop app, not the file.
History, cookies, secret-manager configurationThe data directory, shared with the desktop app by default.
OAuth tokensCached locally by the engine.

The AI features are off until you use them. Vegha doesn’t call a model itself. Copilot, the @vegha participant (which uses the model selected in Chat), or your MCP client makes the model call under its own terms. Before anything reaches a model, Vegha redacts secrets. See Overview & safety.

Vegha is MIT-licensed. The engine source is at github.com/vegha-ai/Vegha.