glintbar 1.0.0__tar.gz

glintbar-1.0.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 paone9
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

glintbar-1.0.0/PKG-INFO

@@ -0,0 +1,242 @@
+Metadata-Version: 2.4
+Name: glintbar
+Version: 1.0.0
+Summary: A slim always-on-top hardware monitor that lives in the empty part of the Windows taskbar.
+Author: paone9
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/paone9/GlintBar
+Project-URL: Issues, https://github.com/paone9/GlintBar/issues
+Keywords: hardware-monitor,taskbar,windows,gpu,cpu,temperature,system-monitor
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Win32 (MS Windows)
+Classifier: Intended Audience :: End Users/Desktop
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: System :: Monitoring
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pywebview>=6.2.1
+Requires-Dist: psutil>=7.2.2
+Dynamic: license-file
+
+# GlintBar
+
+[![CI](https://github.com/paone9/GlintBar/actions/workflows/ci.yml/badge.svg)](https://github.com/paone9/GlintBar/actions/workflows/ci.yml)
+[![CodeQL](https://github.com/paone9/GlintBar/actions/workflows/codeql.yml/badge.svg)](https://github.com/paone9/GlintBar/actions/workflows/codeql.yml)
+[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/paone9/GlintBar/badge)](https://scorecard.dev/viewer/?uri=github.com/paone9/GlintBar)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+
+A small always-on-top hardware monitor that sits in the empty part of your
+Windows taskbar (or docked at the top/bottom). It shows live CPU, RAM, GPU, disk
+and network so you can keep half an eye on them, and it flags thermal, clock or
+power spikes early, before they turn into throttling or a crash like a
+`VIDEO_TDR_FAILURE` GPU hang.
+
+## What it shows
+
+A single row of up to nine metrics, each with a value and a 60-second sparkline.
+Hover a metric to pop out a bigger live graph with the session min, max and
+average.
+
+| Tile | Source | Watch for |
+|------|--------|-----------|
+| GPU Temp | nvidia-smi | amber >80 °C, red >87 °C |
+| GPU Load | nvidia-smi / perf counters | sustained 100% |
+| VRAM | nvidia-smi | red >95 % |
+| GPU Power | nvidia-smi | sudden dropouts under load |
+| GPU Clock | nvidia-smi | dropping to idle mid-load can mean a TDR hang |
+| SYS Temp | ACPI thermal zone | red >97 °C |
+| CPU Temp | LibreHardwareMonitor | real CPU package temp (needs LHM, see below) |
+| Fan | LibreHardwareMonitor | fan RPM (needs LHM, see below) |
+| CPU | psutil | red >95 % |
+| RAM | psutil | red >95 % |
+| Network | psutil | MB/s in+out |
+| Disk | psutil | MB/s read+write |
+
+Everything comes from first-party or open-source sources and runs without admin
+rights. The bar only shows tiles your machine can actually provide (details
+below).
+
+## Supported hardware and platforms
+
+Windows 10/11 only. It uses Win32 APIs, so there's no macOS or Linux build.
+
+CPU, RAM, disk and network work on any Windows PC, via `psutil`.
+
+GPU support is detected at launch:
+
+| GPU | Load | VRAM | Temp | Clock | Power | Source |
+|-----|:----:|:----:|:----:|:-----:|:-----:|--------|
+| NVIDIA | ✅ | ✅ | ✅ | ✅ | ✅ | `nvidia-smi` (driver) |
+| AMD / Intel / other | ✅ | — | — | — | — | Windows GPU perf counters |
+| No GPU / headless | — | — | — | — | — | GPU tiles hidden |
+
+AMD and Intel GPUs get load only. Temp, clock, power and VRAM need NVIDIA. The
+settings panel greys out anything your hardware can't provide.
+
+### Privilege levels: it works without admin, and does more with it
+
+GlintBar itself never needs administrator rights, and it runs fine on its own. At
+normal privilege you get everything except real CPU temperature and fan speed:
+CPU, RAM, disk, network, GPU (per the table above), and the SYS Temp tile.
+
+The SYS Temp tile reads the ACPI thermal zone through a Windows performance
+counter, so it needs no admin. It's a generic zone though, so treat it as a rough
+system-heat reading, not the exact CPU-package sensor, and some machines block it.
+
+Real per-core CPU temperature and fan RPM need kernel-level access, which no
+no-admin tool can do. For those, run a helper that already does the low-level
+reads with admin, and GlintBar reads from it while staying at normal privilege.
+It picks up the extra **CPU Temp** and **Fan** tiles automatically when one is
+present. Two options, whichever you already use:
+
+**HWiNFO** (via shared memory): in HWiNFO, open Settings and tick **Shared Memory
+Support**. That's it. GlintBar reads the shared-memory block directly (no network
+at all). This is easiest if you already run HWiNFO.
+
+**LibreHardwareMonitor** (open source, via a local web server): in its Options
+menu turn on **Remote Web Server** (default port 8085). GlintBar reads only from
+`http://127.0.0.1:8085` on your own machine, never the internet. Use
+`GLINTBAR_LHM_PORT` if you change the port.
+
+Either way, start the helper before GlintBar (or restart GlintBar) and the tiles
+appear on their own. HWiNFO is preferred if both are running.
+
+### Requirements
+
+Python 3.8+ and the WebView2 runtime, which already ships with Windows 11. No
+admin, no compiled binaries, just Python source. The only dependencies are
+`pywebview` and `psutil`, installed automatically.
+
+## Install and run
+
+The simplest one-command install (isolated, adds a `glintbar` command):
+
+```
+pipx install git+https://github.com/paone9/GlintBar
+glintbar
+```
+
+Once it is released on PyPI this becomes `pip install glintbar`.
+
+From a clone, for hacking on it:
+
+```
+pip install -r requirements.txt
+python -m glintbar
+```
+
+For a launch with no console window, double-click `start_glintbar.vbs` (or
+`start_glintbar.cmd` if Windows Script Host is blocked). To start it on login,
+drop a shortcut to the `glintbar` command (or to `start_glintbar.vbs`) into
+`shell:startup` (Win+R, then `shell:startup`).
+
+Controls sit on the right: the gear opens settings, ● toggles CSV logging (it
+turns red while recording), ▤ opens the log folder, and ✕ closes.
+
+Settings and logs live in `%LOCALAPPDATA%\GlintBar` (`config.json` and `logs\`),
+so they survive reinstalls and stay out of the install folder.
+
+## Settings
+
+Open the gear to change:
+
+- Metrics: pick the ones you want, with presets for Essentials, GPU focus, or
+  All. The bar rebuilds and resizes to fit only what you keep.
+- Size: Compact, Normal, or Large.
+- Align: Left, Center, or Right within the taskbar gap.
+- Sparklines, critical alerts, and alert sound: on or off.
+
+Your choices are saved to `config.json` in `%LOCALAPPDATA%\GlintBar`.
+
+## Placement
+
+Set `DOCK` at the top of `glintbar/monitor.py`:
+
+- `"taskbar"` (default) floats a topmost bar over the empty part of the taskbar,
+  between your app buttons and the system tray. It's a normal top-level window
+  that sits above the Windows 11 taskbar's input layer, so its hovers and clicks
+  work and it uses no extra screen space. A small background thread keeps it
+  fitted to the gap and on top as apps open and close.
+- `"bottom"` is a thin full-width strip just above the taskbar.
+- `"top"` is a thin full-width strip at the top of the screen.
+
+It lives on your **primary monitor's** taskbar (the one Windows treats as
+primary), and expects that taskbar along the bottom. On a multi-monitor setup with
+different scaling per monitor it stays correctly placed and sized, since the app is
+per-monitor-DPI aware. Only one copy runs at a time; launching it again just hands
+back to the running one. Letting you pick a different monitor is on the
+[roadmap](ROADMAP.md).
+
+When a video, game, or slideshow goes fullscreen on the same screen, the bar
+hides itself so it's not in the way, and it comes back when you exit fullscreen.
+
+## Hover to expand
+
+Hover a metric and a bigger popup appears just above it with a full 60-second
+graph, the current value, and min/max/avg. It disappears when you move off.
+
+## Critical alerts
+
+When a metric crosses a critical threshold (GPU temp over 87 °C, or CPU, RAM or
+VRAM over 95%), an extra tile appears at the end of the bar. It's added rather
+than swapped in, so your other tiles don't move, and it stays until things settle
+(about two seconds to appear, with a short cooldown before it clears). There's an
+optional beep on a new alert so you notice without watching. Both are toggles in
+settings.
+
+## Away watch
+
+If you step away and the machine keeps working hard, GlintBar figures out what was
+responsible and tells you when you get back. It counts you as away as soon as the
+screen is locked, or after a few minutes with no keyboard or mouse activity. While
+you're away and the CPU stays high, it records which processes are behind it. When
+you return it shows a short summary (how long you were away, the peak CPU and
+temperature, and the busiest processes) and appends a line to `logs/away.csv`. If
+nothing unusual happened, it stays quiet.
+
+Toggle it in settings. The idle delay and CPU threshold are in `config.json`
+(`away_after_min`, `away_cpu_pct`), defaulting to 5 minutes and 25%.
+
+## CSV logging
+
+Press ● to write one row per second to `logs/glintbar_<timestamp>.csv` with every
+metric. Open it in pandas or Excel and line it up against a workload timeline to
+see how throttling, thermal drift or power dropouts track with load.
+
+```python
+import pandas as pd
+df = pd.read_csv("logs/glintbar_<timestamp>.csv", parse_dates=["timestamp"])
+df.set_index("timestamp")[["gpu_temp", "gpu_clock", "gpu_power"]].plot()
+```
+
+## Notes
+
+- It adapts to any resolution and display scaling; DPI is read at runtime.
+- Light footprint: CPU, RAM, disk and network update every second, while the GPU
+  (which means spawning `nvidia-smi`) is polled every two seconds and cached in
+  between, so the monitor itself stays cheap.
+- Thresholds live in the `META` map at the top of `glintbar/ui.html`, so they're
+  easy to change.
+- Ideas that aren't built yet (attention rotation, anomaly detection, toast
+  notifications, AMD/Intel temperatures) are written up in [ROADMAP.md](ROADMAP.md).
+
+## Security
+
+GlintBar is meant to be easy to review. It's plain Python with no binaries and no
+obfuscation, it needs no admin, and it makes no network connections at all: no
+telemetry, no update checks, nothing. It only reads system metrics and writes
+`config.json` and logs inside its own folder.
+
+CI runs `ruff` and `bandit` on every push, and a `CodeQL` workflow runs semantic
+static analysis of the Python, the UI JavaScript, and the workflows themselves.
+GitHub Actions are pinned to commit SHAs and the two dependencies are pinned to
+their tested versions, so the build can't shift under you. An
+[OpenSSF Scorecard](https://scorecard.dev/viewer/?uri=github.com/paone9/GlintBar)
+grades the repo's security posture (badge above). See the repo's Security tab, and
+[SECURITY.md](SECURITY.md) for exactly what the app touches.
+
+## License
+
+MIT. See [LICENSE](LICENSE).

glintbar-1.0.0/README.md

@@ -0,0 +1,220 @@
+# GlintBar
+
+[![CI](https://github.com/paone9/GlintBar/actions/workflows/ci.yml/badge.svg)](https://github.com/paone9/GlintBar/actions/workflows/ci.yml)
+[![CodeQL](https://github.com/paone9/GlintBar/actions/workflows/codeql.yml/badge.svg)](https://github.com/paone9/GlintBar/actions/workflows/codeql.yml)
+[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/paone9/GlintBar/badge)](https://scorecard.dev/viewer/?uri=github.com/paone9/GlintBar)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+
+A small always-on-top hardware monitor that sits in the empty part of your
+Windows taskbar (or docked at the top/bottom). It shows live CPU, RAM, GPU, disk
+and network so you can keep half an eye on them, and it flags thermal, clock or
+power spikes early, before they turn into throttling or a crash like a
+`VIDEO_TDR_FAILURE` GPU hang.
+
+## What it shows
+
+A single row of up to nine metrics, each with a value and a 60-second sparkline.
+Hover a metric to pop out a bigger live graph with the session min, max and
+average.
+
+| Tile | Source | Watch for |
+|------|--------|-----------|
+| GPU Temp | nvidia-smi | amber >80 °C, red >87 °C |
+| GPU Load | nvidia-smi / perf counters | sustained 100% |
+| VRAM | nvidia-smi | red >95 % |
+| GPU Power | nvidia-smi | sudden dropouts under load |
+| GPU Clock | nvidia-smi | dropping to idle mid-load can mean a TDR hang |
+| SYS Temp | ACPI thermal zone | red >97 °C |
+| CPU Temp | LibreHardwareMonitor | real CPU package temp (needs LHM, see below) |
+| Fan | LibreHardwareMonitor | fan RPM (needs LHM, see below) |
+| CPU | psutil | red >95 % |
+| RAM | psutil | red >95 % |
+| Network | psutil | MB/s in+out |
+| Disk | psutil | MB/s read+write |
+
+Everything comes from first-party or open-source sources and runs without admin
+rights. The bar only shows tiles your machine can actually provide (details
+below).
+
+## Supported hardware and platforms
+
+Windows 10/11 only. It uses Win32 APIs, so there's no macOS or Linux build.
+
+CPU, RAM, disk and network work on any Windows PC, via `psutil`.
+
+GPU support is detected at launch:
+
+| GPU | Load | VRAM | Temp | Clock | Power | Source |
+|-----|:----:|:----:|:----:|:-----:|:-----:|--------|
+| NVIDIA | ✅ | ✅ | ✅ | ✅ | ✅ | `nvidia-smi` (driver) |
+| AMD / Intel / other | ✅ | — | — | — | — | Windows GPU perf counters |
+| No GPU / headless | — | — | — | — | — | GPU tiles hidden |
+
+AMD and Intel GPUs get load only. Temp, clock, power and VRAM need NVIDIA. The
+settings panel greys out anything your hardware can't provide.
+
+### Privilege levels: it works without admin, and does more with it
+
+GlintBar itself never needs administrator rights, and it runs fine on its own. At
+normal privilege you get everything except real CPU temperature and fan speed:
+CPU, RAM, disk, network, GPU (per the table above), and the SYS Temp tile.
+
+The SYS Temp tile reads the ACPI thermal zone through a Windows performance
+counter, so it needs no admin. It's a generic zone though, so treat it as a rough
+system-heat reading, not the exact CPU-package sensor, and some machines block it.
+
+Real per-core CPU temperature and fan RPM need kernel-level access, which no
+no-admin tool can do. For those, run a helper that already does the low-level
+reads with admin, and GlintBar reads from it while staying at normal privilege.
+It picks up the extra **CPU Temp** and **Fan** tiles automatically when one is
+present. Two options, whichever you already use:
+
+**HWiNFO** (via shared memory): in HWiNFO, open Settings and tick **Shared Memory
+Support**. That's it. GlintBar reads the shared-memory block directly (no network
+at all). This is easiest if you already run HWiNFO.
+
+**LibreHardwareMonitor** (open source, via a local web server): in its Options
+menu turn on **Remote Web Server** (default port 8085). GlintBar reads only from
+`http://127.0.0.1:8085` on your own machine, never the internet. Use
+`GLINTBAR_LHM_PORT` if you change the port.
+
+Either way, start the helper before GlintBar (or restart GlintBar) and the tiles
+appear on their own. HWiNFO is preferred if both are running.
+
+### Requirements
+
+Python 3.8+ and the WebView2 runtime, which already ships with Windows 11. No
+admin, no compiled binaries, just Python source. The only dependencies are
+`pywebview` and `psutil`, installed automatically.
+
+## Install and run
+
+The simplest one-command install (isolated, adds a `glintbar` command):
+
+```
+pipx install git+https://github.com/paone9/GlintBar
+glintbar
+```
+
+Once it is released on PyPI this becomes `pip install glintbar`.
+
+From a clone, for hacking on it:
+
+```
+pip install -r requirements.txt
+python -m glintbar
+```
+
+For a launch with no console window, double-click `start_glintbar.vbs` (or
+`start_glintbar.cmd` if Windows Script Host is blocked). To start it on login,
+drop a shortcut to the `glintbar` command (or to `start_glintbar.vbs`) into
+`shell:startup` (Win+R, then `shell:startup`).
+
+Controls sit on the right: the gear opens settings, ● toggles CSV logging (it
+turns red while recording), ▤ opens the log folder, and ✕ closes.
+
+Settings and logs live in `%LOCALAPPDATA%\GlintBar` (`config.json` and `logs\`),
+so they survive reinstalls and stay out of the install folder.
+
+## Settings
+
+Open the gear to change:
+
+- Metrics: pick the ones you want, with presets for Essentials, GPU focus, or
+  All. The bar rebuilds and resizes to fit only what you keep.
+- Size: Compact, Normal, or Large.
+- Align: Left, Center, or Right within the taskbar gap.
+- Sparklines, critical alerts, and alert sound: on or off.
+
+Your choices are saved to `config.json` in `%LOCALAPPDATA%\GlintBar`.
+
+## Placement
+
+Set `DOCK` at the top of `glintbar/monitor.py`:
+
+- `"taskbar"` (default) floats a topmost bar over the empty part of the taskbar,
+  between your app buttons and the system tray. It's a normal top-level window
+  that sits above the Windows 11 taskbar's input layer, so its hovers and clicks
+  work and it uses no extra screen space. A small background thread keeps it
+  fitted to the gap and on top as apps open and close.
+- `"bottom"` is a thin full-width strip just above the taskbar.
+- `"top"` is a thin full-width strip at the top of the screen.
+
+It lives on your **primary monitor's** taskbar (the one Windows treats as
+primary), and expects that taskbar along the bottom. On a multi-monitor setup with
+different scaling per monitor it stays correctly placed and sized, since the app is
+per-monitor-DPI aware. Only one copy runs at a time; launching it again just hands
+back to the running one. Letting you pick a different monitor is on the
+[roadmap](ROADMAP.md).
+
+When a video, game, or slideshow goes fullscreen on the same screen, the bar
+hides itself so it's not in the way, and it comes back when you exit fullscreen.
+
+## Hover to expand
+
+Hover a metric and a bigger popup appears just above it with a full 60-second
+graph, the current value, and min/max/avg. It disappears when you move off.
+
+## Critical alerts
+
+When a metric crosses a critical threshold (GPU temp over 87 °C, or CPU, RAM or
+VRAM over 95%), an extra tile appears at the end of the bar. It's added rather
+than swapped in, so your other tiles don't move, and it stays until things settle
+(about two seconds to appear, with a short cooldown before it clears). There's an
+optional beep on a new alert so you notice without watching. Both are toggles in
+settings.
+
+## Away watch
+
+If you step away and the machine keeps working hard, GlintBar figures out what was
+responsible and tells you when you get back. It counts you as away as soon as the
+screen is locked, or after a few minutes with no keyboard or mouse activity. While
+you're away and the CPU stays high, it records which processes are behind it. When
+you return it shows a short summary (how long you were away, the peak CPU and
+temperature, and the busiest processes) and appends a line to `logs/away.csv`. If
+nothing unusual happened, it stays quiet.
+
+Toggle it in settings. The idle delay and CPU threshold are in `config.json`
+(`away_after_min`, `away_cpu_pct`), defaulting to 5 minutes and 25%.
+
+## CSV logging
+
+Press ● to write one row per second to `logs/glintbar_<timestamp>.csv` with every
+metric. Open it in pandas or Excel and line it up against a workload timeline to
+see how throttling, thermal drift or power dropouts track with load.
+
+```python
+import pandas as pd
+df = pd.read_csv("logs/glintbar_<timestamp>.csv", parse_dates=["timestamp"])
+df.set_index("timestamp")[["gpu_temp", "gpu_clock", "gpu_power"]].plot()
+```
+
+## Notes
+
+- It adapts to any resolution and display scaling; DPI is read at runtime.
+- Light footprint: CPU, RAM, disk and network update every second, while the GPU
+  (which means spawning `nvidia-smi`) is polled every two seconds and cached in
+  between, so the monitor itself stays cheap.
+- Thresholds live in the `META` map at the top of `glintbar/ui.html`, so they're
+  easy to change.
+- Ideas that aren't built yet (attention rotation, anomaly detection, toast
+  notifications, AMD/Intel temperatures) are written up in [ROADMAP.md](ROADMAP.md).
+
+## Security
+
+GlintBar is meant to be easy to review. It's plain Python with no binaries and no
+obfuscation, it needs no admin, and it makes no network connections at all: no
+telemetry, no update checks, nothing. It only reads system metrics and writes
+`config.json` and logs inside its own folder.
+
+CI runs `ruff` and `bandit` on every push, and a `CodeQL` workflow runs semantic
+static analysis of the Python, the UI JavaScript, and the workflows themselves.
+GitHub Actions are pinned to commit SHAs and the two dependencies are pinned to
+their tested versions, so the build can't shift under you. An
+[OpenSSF Scorecard](https://scorecard.dev/viewer/?uri=github.com/paone9/GlintBar)
+grades the repo's security posture (badge above). See the repo's Security tab, and
+[SECURITY.md](SECURITY.md) for exactly what the app touches.
+
+## License
+
+MIT. See [LICENSE](LICENSE).

glintbar-1.0.0/glintbar/__init__.py

@@ -0,0 +1,3 @@
+"""GlintBar - a slim always-on-top hardware monitor for the Windows taskbar gap."""
+
+__version__ = "1.0.0"

glintbar-1.0.0/glintbar/__main__.py

@@ -0,0 +1,6 @@
+"""Entry point for `python -m glintbar`."""
+
+from .monitor import main
+
+if __name__ == "__main__":
+    main()

glintbar-1.0.0/glintbar/away.html

@@ -0,0 +1,69 @@
+<meta charset="utf-8">
+<style>
+  :root{ --bg:#12161c; --line:#2b3542; --text:#e6edf3; --dim:#9aa4af;
+         --ok:#58a6ff; --warn:#d29922; --crit:#f85149; }
+  *{ box-sizing:border-box; margin:0; padding:0; }
+  html,body{ height:100%; }
+  body{ background:transparent; color:var(--text);
+        font:12px/1.35 "Segoe UI",system-ui,sans-serif; overflow:hidden; }
+  .card{ height:100vh; background:var(--bg); border:1px solid var(--line);
+         border-radius:10px; padding:12px 14px; box-shadow:0 8px 26px #000a;
+         display:flex; flex-direction:column; }
+  .hdr{ font-size:14px; font-weight:700; }
+  .sub{ font-size:11px; color:var(--dim); margin:1px 0 10px; }
+  .row{ display:flex; justify-content:space-between; font-size:12px; padding:2px 0; }
+  .row .k{ color:var(--dim); }
+  .row .v{ font-weight:600; font-variant-numeric:tabular-nums; }
+  .v.hot{ color:var(--crit); }
+  .lbl{ font-size:10px; text-transform:uppercase; letter-spacing:.06em;
+        color:var(--dim); margin:10px 0 4px; }
+  .proc{ display:flex; justify-content:space-between; font-size:12px; padding:2px 0;
+         border-top:1px solid #ffffff10; }
+  .proc .p{ overflow:hidden; text-overflow:ellipsis; white-space:nowrap; }
+  .proc .c{ color:var(--warn); font-weight:600; font-variant-numeric:tabular-nums;
+            padding-left:8px; }
+  .actions{ display:flex; gap:8px; margin-top:auto; padding-top:10px; }
+  .actions button{ flex:1; padding:7px; border-radius:6px; font-size:12px; cursor:pointer;
+        border:1px solid var(--line); background:#1b2430; color:var(--text); }
+  .actions .go{ border-color:var(--ok); color:var(--ok); }
+</style>
+
+<div class="card">
+  <div class="hdr">While you were away</div>
+  <div class="sub" id="sub">—</div>
+  <div class="row"><span class="k">Peak CPU</span><span class="v" id="cpu">—</span></div>
+  <div class="row"><span class="k">Peak system temp</span><span class="v" id="temp">—</span></div>
+  <div class="lbl">Busiest processes</div>
+  <div id="procs"></div>
+  <div class="actions">
+    <button id="logs">Open log</button>
+    <button class="go" id="dismiss">Got it</button>
+  </div>
+</div>
+
+<script>
+async function tick(){
+  let r; try{ r = await window.pywebview.api.get(); }catch(e){ return; }
+  if(!r) return;
+  document.getElementById("sub").textContent = `${r.when}, away for ${r.duration_min} min`;
+  const cpu = document.getElementById("cpu");
+  cpu.textContent = r.peak_cpu + "%"; cpu.className = "v" + (r.peak_cpu >= 60 ? " hot" : "");
+  const temp = document.getElementById("temp");
+  temp.textContent = r.peak_temp ? r.peak_temp + " °C" : "n/a";
+  temp.className = "v" + (r.peak_temp >= 90 ? " hot" : "");
+  const host = document.getElementById("procs"); host.innerHTML = "";
+  const list = r.offenders || [];
+  if(list.length){
+    for(const [name, c] of list){
+      const d = document.createElement("div"); d.className = "proc";
+      d.innerHTML = `<span class="p">${name}</span><span class="c">${c}%</span>`;
+      host.appendChild(d);
+    }
+  } else {
+    host.innerHTML = `<div class="proc"><span class="p">nothing stood out</span></div>`;
+  }
+}
+document.getElementById("logs").onclick = ()=> window.pywebview.api.open_logs();
+document.getElementById("dismiss").onclick = ()=> window.pywebview.api.dismiss();
+window.addEventListener("pywebviewready", ()=>{ tick(); setInterval(tick, 1000); });
+</script>

glintbar-1.0.0/glintbar/detail.html

@@ -0,0 +1,88 @@
+<meta charset="utf-8">
+<style>
+  :root{ --bg:#12161c; --line:#2b3542; --text:#e6edf3; --dim:#9aa4af;
+         --ok:#58a6ff; --warn:#d29922; --crit:#f85149; }
+  *{ box-sizing:border-box; margin:0; padding:0; }
+  html,body{ height:100%; }
+  body{ background:transparent; color:var(--text);
+        font:12px/1.2 "Segoe UI",system-ui,sans-serif; overflow:hidden; }
+  .card{ height:100vh; background:var(--bg); border:1px solid var(--line);
+         border-radius:10px; padding:9px 11px; box-shadow:0 6px 22px #000a; }
+  .top{ display:flex; justify-content:space-between; align-items:baseline; }
+  .lbl{ font-size:11px; text-transform:uppercase; letter-spacing:.06em; color:var(--dim); }
+  .val{ font-size:22px; font-weight:700; font-variant-numeric:tabular-nums; }
+  .val .u{ font-size:12px; color:var(--dim); font-weight:400; }
+  .stats{ font-size:11px; color:var(--dim); margin-top:1px; }
+  canvas{ width:100%; height:96px; margin-top:6px; display:block; }
+  .val.ok{ color:var(--text); } .val.warn{ color:var(--warn); } .val.crit{ color:var(--crit); }
+</style>
+<div class="card">
+  <div class="top"><span class="lbl" id="lbl">—</span>
+    <span class="val ok" id="val">—</span></div>
+  <div class="stats" id="stats"></div>
+  <canvas id="cv" width="600" height="220"></canvas>
+</div>
+
+<script>
+const META = {
+  gpu_temp:{lbl:"GPU Temperature",unit:"°C",warn:80,crit:87,max:100},
+  gpu_util:{lbl:"GPU Load",unit:"%",warn:1e9,crit:1e9,max:100},
+  gpu_mem_pct:{lbl:"VRAM Used",unit:"%",warn:85,crit:95,max:100},
+  gpu_power:{lbl:"GPU Power",unit:"W",warn:1e9,crit:1e9,max:130},
+  gpu_clock:{lbl:"GPU Clock",unit:"MHz",warn:1e9,crit:1e9,max:2200},
+  sys_temp:{lbl:"System Temp (ACPI zone)",unit:"°C",warn:85,crit:97,max:110},
+  cpu_temp:{lbl:"CPU Temperature",unit:"°C",warn:85,crit:97,max:110},
+  fan_rpm:{lbl:"Fan Speed",unit:"RPM",warn:1e9,crit:1e9,max:6000},
+  cpu:{lbl:"CPU Load",unit:"%",warn:85,crit:95,max:100},
+  ram_pct:{lbl:"RAM Used",unit:"%",warn:85,crit:95,max:100},
+  net_mbps:{lbl:"Network",unit:"MB/s",warn:1e9,crit:1e9,max:50,dyn:true},
+  disk_mbps:{lbl:"Disk",unit:"MB/s",warn:1e9,crit:1e9,max:200,dyn:true},
+};
+function cls(m,v){ if(v==null)return"ok"; if(v>=m.crit)return"crit"; if(v>=m.warn)return"warn"; return"ok"; }
+function fmt(v,id){ if(v==null)return"—";
+  if(id==="net_mbps"||id==="disk_mbps"||id==="gpu_power")return v.toFixed(1); return Math.round(v); }
+function gv(n){ return getComputedStyle(document.documentElement).getPropertyValue(n).trim(); }
+function color(c){ return c==="crit"?gv("--crit"):c==="warn"?gv("--warn"):gv("--ok"); }
+
+function draw(cv,data,m,colr){
+  const ctx=cv.getContext("2d"), w=cv.width, h=cv.height, pad=6;
+  ctx.clearRect(0,0,w,h);
+  // baseline grid
+  ctx.strokeStyle="#ffffff14"; ctx.lineWidth=1;
+  for(let i=0;i<=2;i++){ const y=pad+(h-2*pad)*i/2; ctx.beginPath(); ctx.moveTo(0,y); ctx.lineTo(w,y); ctx.stroke(); }
+  if(!data.length) return;
+  let top = m.dyn ? Math.max(...data,1)*1.2 : m.max;
+  const n=data.length, sx=w/Math.max(n-1,1);
+  ctx.beginPath();
+  data.forEach((v,i)=>{ const y=h-pad-(Math.min((v==null?0:v),top)/top)*(h-2*pad); const x=i*sx;
+    i===0?ctx.moveTo(x,y):ctx.lineTo(x,y); });
+  ctx.strokeStyle=colr; ctx.lineWidth=2.5; ctx.lineJoin="round"; ctx.stroke();
+  ctx.lineTo((n-1)*sx,h); ctx.lineTo(0,h); ctx.closePath(); ctx.fillStyle=colr+"22"; ctx.fill();
+}
+
+let lastMetric = null;
+async function tick(){
+  let d; try{ d=await window.pywebview.api.get(); }catch(e){ return; }
+  if(!d || !d.metric){ lastMetric=null; return; }
+  const m=META[d.metric]; if(!m) return;
+  if(d.metric !== lastMetric){   // new tile: wipe the previous frame before drawing this one
+    lastMetric = d.metric;
+    document.getElementById("stats").textContent = "";
+    const c0=document.getElementById("cv"); c0.getContext("2d").clearRect(0,0,c0.width,c0.height);
+  }
+  const v=d.latest, c=cls(m,v);
+  document.getElementById("lbl").textContent = m.lbl;
+  const val=document.getElementById("val"); val.className="val "+c;
+  val.innerHTML = fmt(v,d.metric)+` <span class="u">${m.unit}</span>`;
+  const s=d.stats||{};
+  let extra="";
+  if(d.metric==="gpu_mem_pct"&&d.extra&&d.extra.gpu_mem_used!=null)
+    extra=`  ·  ${Math.round(d.extra.gpu_mem_used)}/${Math.round(d.extra.gpu_mem_total)} MB`;
+  if(d.metric==="ram_pct"&&d.extra&&d.extra.ram_used_gb!=null)
+    extra=`  ·  ${d.extra.ram_used_gb.toFixed(1)}/${d.extra.ram_total_gb.toFixed(0)} GB`;
+  document.getElementById("stats").textContent =
+    (s.min!=null?`min ${fmt(s.min,d.metric)}  ·  max ${fmt(s.max,d.metric)}  ·  avg ${fmt(s.avg,d.metric)}  ·  last 60s`:"") + extra;
+  draw(document.getElementById("cv"), d.hist||[], m, color(c));
+}
+window.addEventListener("pywebviewready", ()=>{ tick(); setInterval(tick, 100); });
+</script>