Installation

Requirements

• VS Code 1.101 or later (or a compatible editor such as Cursor or VSCodium).
• Windows, macOS or Linux on x64 or arm64.

Nothing else. Each platform’s package includes a self-contained Vegha engine, so you don’t need .NET, Node or the Vegha desktop app.

From the Marketplace

1. Open the Extensions view (Ctrl+Shift+X / Cmd+Shift+X).
2. Search for Vegha and pick Vegha — API Client published by Vegha.
3. Select Install.

Or from a terminal:

code --install-extension vegha.vegha

Listing: marketplace.visualstudio.com/items?itemName=vegha.vegha

From Open VSX

Editors that use Open VSX (VSCodium, Gitpod, Eclipse Theia and others) install it from their own Extensions view the same way.

From a VSIX file

Each release is also published as one .vsix per platform, such as vegha-win32-x64.vsix or vegha-darwin-arm64.vsix. Install one with Extensions: Install from VSIX… in the Command Palette, or:

code --install-extension vegha-linux-x64.vsix

Use the file that matches your editor’s platform. A Windows-on-Arm or Apple Silicon machine needs the arm64 build.

Remote, WSL and containers

The extension runs on the workspace side. In a Remote-SSH, WSL or Dev Container window it installs into the remote host and sends requests from there, so localhost means the remote machine.

Updating

VS Code updates the extension automatically. If you set up MCP for another agent, run Vegha: Set Up MCP for Other Agents… again after an update, because the copied command points into the installed extension version.

Uninstalling

Uninstalling the extension doesn’t touch your collections. They are ordinary files in your workspace. History and cookies stay in the data directory.