Skip to main content
The HyperProbe VS Code extension puts the full probe workflow inside your editor. Once installed, you can insert snapshots, logs, counters, and metrics directly from the file you are working in — without switching to a separate tool or browser tab.

​
Requirements

Before you install, confirm your environment meets the minimum requirements:

VS Code 1.85 or later

Open Help → About in VS Code to check your version. Update from the VS Code download page if needed.

A running HyperProbe server

The extension connects to a HyperProbe backend. You need either the self-hosted server or access to https://app.hyperprobe.com.

​
Install from the marketplace

1

Open the Extensions view

Press Ctrl+Shift+X (Windows / Linux) or Cmd+Shift+X (macOS) to open the Extensions panel, or click the Extensions icon in the Activity Bar.
2

Search for HyperProbe

Type HyperProbe in the search box. The extension is published by hyperprobe and listed under the Debuggers category.
3

Install the extension

Click Install on the HyperProbe result. VS Code downloads and activates the extension immediately — no reload is required.
4

Verify the installation

Look for the HyperProbe icon (a debug-console symbol) in the Activity Bar on the left side of the editor. Clicking it opens the HyperProbe panel.

​
Add a .hprc file to your project

The extension discovers which service a workspace belongs to by reading .hprc files. Each .hprc file is a small JSON file that maps the workspace (or a subdirectory within a monorepo) to a HyperProbe service ID. Create a .hprc file in your project root:
.hprc
{
  "serviceId": "my-service"
}
Replace "my-service" with the service ID you used when initializing the HyperProbe SDK in your application.
In a monorepo, you can place a .hprc file inside each package directory. The extension scans the entire workspace for .hprc files and registers all service IDs it finds. It also watches for changes, so you do not need to reload VS Code after adding or editing a .hprc file.
Once the extension detects a .hprc file, the service ID becomes available in the Source selector when you create a new probe. If the service ID does not appear, confirm that the serviceId field in your .hprc is a valid string and that the file is saved inside the VS Code workspace.

​
Next steps

Configure the extension

Set your server URL, configure certificate pinning, and learn about available settings.

Start using probes

Insert your first snapshot, log, or counter from inside the editor.