Keep real laptop readings in view.

Start the connection

Download HP laptop connector

1. Install Node.js 24 or later if needed.
2. Extract the ZIP. Open the gabriel-hp-live folder in Terminal or PowerShell.
3. Type node monitor.mjs and press Enter.
4. Open the http://127.0.0.1:… address printed in the terminal.
5. Keep the terminal open to continue monitoring. Use the dashboard’s Stop monitoring button or press Ctrl+C in the terminal to stop.

No administrator access is requested. Source code and instructions are included in the download.

What is connected

The local dashboard reads Windows software counters. Collection failures trigger another bounded read; old readings are withheld from live status. Up to 60 recent samples stay in memory and clear when the process exits.

Optional disk or battery readings remain unknown when Windows does not provide them. These counters do not establish the exact origin or spread of a fault.

Run the participant test

In the local dashboard, paste your submitted signal reference and a website hostname to check. Start with the optional correction checkbox off, then choose Start this scoped test and Check hostname now.

The dashboard shows signal binding, current counters, available tools, correction policy and observed results. The hostname check runs once per minute while its session remains active. This is a local participant test; entering a reference does not authenticate a hosted case.

Optional automatic correction

You can allow one Windows DNS cache reset per connector run. It requires two failed system hostname lookups, a successful direct resolver query and fresh laptop readings. It clears the entire local Windows DNS cache, including other applications’ entries, then checks the hostname again. Temporary cache entries rebuild through later lookups; no prior cache snapshot is restored. A successful lookup afterward does not prove the action caused recovery.

This is a specific lookup-path correction, not a general repair for a slow laptop. Healthy lookups trigger no action. Failed commands, unchanged results and unsupported evidence remain visible. The connector does not elevate privileges, close applications, reboot or change DNS servers.

Physical voltage, temperature and vibration interfaces and hosted live-case upload are still not connected. Other repairs require their own implemented adapters and scoped policies.