JVM Pulse brings the existing local JVM monitor into a VS Code editor tab. It discovers local JVMs and shows CPU, heap, threads, classes, garbage collection, JFR recordings, class histograms, and heap diagnostics.
Requirements
Windows 10 or newer (the current JVM Pulse diagnostics and MAT integration target Windows)
A full JDK 21 or newer; a JRE is not enough
The extension host and monitored JVM must run as the same OS user
Development
The server directory contains the packaged output of the sibling JVM-Pulse project. Refresh it after changing the Java backend:
.\build-server.ps1
npm install
npm run compile
Press F5 and run JVM Pulse: Open Monitor. For a VSIX, run npm run package after build-server.ps1, then package with npx @vscode/vsce package.
Set jvmPulse.javaHome if VS Code cannot find the correct JDK. Port 0 chooses an available loopback port automatically.
