Free diagnostic

Check your Windows AI coding setup in 5 minutes

Use this before buying the full kit. It helps you identify whether the problem is Node.js, npm PATH, Electron, native modules, node-gyp, Build Tools, audio capture, or Push-to-Talk key listening.

Get the full recovery kit View on Product Hunt
1

Confirm Node.js and npm are visible

If npm is not recognized, the current terminal probably does not have Node.js on PATH.

node -v
npm -v
where node
where npm

Expected: Node.js 24+ and a real path for both node and npm. If Node works but npm does not, close PowerShell, open a new one, and test again.

2

Check the project install state

Run this from the project folder only. It should finish without reinstalling Node.js globally.

npm install
npm run dev

If Electron says it failed to install correctly, the full kit gives a clean reinstall path for the Electron package.

3

Identify native-module failures

Native dependencies often need prebuilt binaries. When prebuilds are unavailable, Windows may need Visual Studio Build Tools or MinGW-w64.

npm ls better-sqlite3
npm rebuild

Do not install build tools blindly. First check whether the failing package has a prebuilt binary for your Node and Electron version.

4

Understand Push-to-Talk fallback mode

windows-key-listener fallback mode means the app can still use a fallback approach, but a compiled native listener may be unavailable.

# If the app still runs, test the fallback first.
# If hotkeys fail, then check build tools or tap mode.

The paid kit includes the practical decision order: when to accept fallback, when to compile locally, and when to switch mode.

When the full kit is worth it

Buy it if you hit one of these: npm is not recognized, Electron failed to install correctly, native module rebuild errors, or Push-to-Talk listener fallback that breaks your workflow.

Get the full recovery kit for 13 USD

Independent practical material. Not an official OpenAI, Codex, or OpenWhispr product.