ccdeck 3.38.4 → 3.38.6

package/dist/web/index.html

@@ -64,8 +64,8 @@
           stored === "light" || (stored !== "dark" && light) ? "light" : "dark");
       })();
     </script>
-    <script type="module" crossorigin src="/assets/index-FnWpX0X5.js"></script>
-    <link rel="stylesheet" crossorigin href="/assets/index-6_mJZ_aP.css">
+    <script type="module" crossorigin src="/assets/index-BKLXyjIh.js"></script>
+    <link rel="stylesheet" crossorigin href="/assets/index-DnJPDhs9.css">
   </head>
   <body>
     <div id="root"></div>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ccdeck",
-  "version": "3.38.4",
+  "version": "3.38.6",
   "description": "Local dashboard for Claude Code and Codex CLI sessions: which Claude Code session needs input, every tool call and Claude Code subagent live, token cost and quota, several Claude accounts. Run npx ccdeck.",
   "type": "module",
   "bin": {

package/release-notes.json

@@ -72,7 +72,18 @@
     "3.37.0",
     "3.38.0",
     "3.38.1",
-    "3.38.2"
+    "3.38.2",
+    "3.38.6"
+  ],
+  "3.38.5": [
+    {
+      "title": "🔧 Settings are in one place now",
+      "body": "The theme, the sounds, notifications, Claude FM and the minimap character are all in Settings, behind the gear at the right of the topbar, or Cmd+, (Ctrl+, on Windows and Linux). The speaker beside it keeps the quick things one click away: sounds on or off, and how loud each tone is. Nothing you had set has changed, it has only moved, and T still switches the theme. The auto-switch threshold also takes a custom value now: pick Custom… and type a whole percent from 50 to 99."
+    },
+    {
+      "title": "Windows: no more temperature stuck at 28 °C",
+      "body": "On many Windows laptops the only temperature Windows offers is a thermal zone wired to nothing, which reads a fixed 28 °C however hot the CPU is, and the machine panel showed it as a reading. A thermal zone is now drawn only once its value has changed. Until then the panel shows LibreHardwareMonitor's readings if its web server is running, and otherwise no Thermal section at all: the deck never invents a reading."
+    }
   ],
   "3.38.4": [
     {

package/src/server/thermal-metrics.mjs

@@ -111,10 +111,19 @@ import { run } from "./metrics-run.mjs";
 //            Reasoned from the documented layout, not yet run on a localised
 //            Windows.
 //
-//            A MODERN INTEL LAPTOP declares no zone at all: Intel DTT manages
-//            its sensors and publishes them only to an administrator. There the
-//            degrees come from LibreHardwareMonitor's local web server when the
-//            user already runs it — see hwmonitor.mjs.
+//            A ZONE IS NOT THE CPU, AND IT MAY NOT BE A SENSOR AT ALL. An ACPI
+//            zone measures whatever the firmware wired it to — the skin, the
+//            board, the embedded controller's idea of the hottest of those —
+//            and on a lot of laptops it measures nothing: Intel's reference
+//            firmware returns a constant 3010 (drawn as 28°C) when it has no
+//            source. So a zone is drawn only once it has been seen to change,
+//            and never under the name CPU. See zonesSeenAfter.
+//
+//            A MODERN INTEL LAPTOP declares no zone at all, or one that never
+//            moves: Intel DTT manages its sensors and publishes them only to an
+//            administrator. There the degrees come from LibreHardwareMonitor's
+//            local web server when the user already runs it — see
+//            hwmonitor.mjs.
 //
 // NEVER INVENT A READING. No sensor means no row, and no rows at all means the
 // section is not rendered: not 0°C, not a dash, not a grey empty bar. Same rule
@@ -599,31 +608,93 @@ export async function readThermal(platform = process.platform, since = null) {
     return darwinThermal({ gpuC, throttle, macmon });
   }
 
-  if (platform === "win32") {
-    // One child for both sources rather than two, because the cost here is the
-    // PowerShell start and not the queries: the counter is tried first because
-    // it needs no administrator, and MSAcpi only when the counter said nothing.
-    // Both are wrapped in their own try — "no thermal zone on this machine" is
-    // the ordinary answer and arrives as a throw from either.
-    const out = await run("powershell.exe", [
-      "-NoProfile", "-NonInteractive", "-Command", WIN_THERMAL_PS,
-    ], 6_000);
-    const answer = out ? parseWinThermal(out.trim()) : [];
-    if (answer.length) return { celsius: answer, throttle: null };
-
-    // Windows itself had nothing, which on a modern Intel laptop is every time:
-    // the firmware declares no ACPI thermal zone and the sensors sit behind
-    // Intel DTT, which an ordinary process may not read. If something on this
-    // machine has already gone and got them — LibreHardwareMonitor, with its
-    // web server on — they are a plain HTTP read away. Never installed, never
-    // asked for. See hwmonitor.mjs.
-    const { readHwMonitorTemps } = await import("./hwmonitor.mjs");
-    const t = await readHwMonitorTemps();
-    const rows = [];
-    if (t.cpu != null) rows.push({ label: "CPU", celsius: t.cpu, warnAt: WARN_C, critAt: CRIT_C });
-    if (t.gpu != null) rows.push({ label: "GPU", celsius: t.gpu, warnAt: WARN_C, critAt: CRIT_C });
-    return rows.length ? { celsius: rows, throttle: null } : null;
-  }
+  if (platform === "win32") return readWindowsThermal(since);
 
   return null;
 }
+
+/**
+ * The Windows rows, from the PowerShell child and, failing that, from a running
+ * LibreHardwareMonitor.
+ *
+ * `deps` is a seam for the reason sampleThermal's `deps.read` is: the suite
+ * must never start PowerShell, so `powershell` stands in for the child's output
+ * and `hwMonitor` for the read of the local web server.
+ */
+export async function readWindowsThermal(since = null, deps = {}) {
+  // One child for both sources rather than two, because the cost here is the
+  // PowerShell start and not the queries: the counter is tried first because
+  // it needs no administrator, and MSAcpi only when the counter said nothing.
+  // Both are wrapped in their own try — "no thermal zone on this machine" is
+  // the ordinary answer and arrives as a throw from either.
+  const powershell = deps.powershell ?? (() => run("powershell.exe", [
+    "-NoProfile", "-NonInteractive", "-Command", WIN_THERMAL_PS,
+  ], 6_000));
+  const hwMonitor = deps.hwMonitor
+    ?? (async () => (await import("./hwmonitor.mjs")).readHwMonitorTemps());
+
+  const out = await powershell();
+  const zones = out ? parseWinThermal(out.trim()) : [];
+  const zonesSeen = zonesSeenAfter(zones, since?.zonesSeen);
+  const memory = Object.keys(zonesSeen).length ? { zonesSeen } : {};
+  const moved = zones.filter(z => zonesSeen[z.label].moved);
+  if (moved.length) return { celsius: moved, throttle: null, ...memory };
+
+  // Windows had no zone that has moved, which on a modern Intel laptop is
+  // every time: the firmware declares no ACPI thermal zone, or declares one
+  // that returns a constant, and the sensors sit behind Intel DTT, which an
+  // ordinary process may not read. If something on this machine has already
+  // gone and got them — LibreHardwareMonitor, with its web server on — they
+  // are a plain HTTP read away. Never installed, never asked for. See
+  // hwmonitor.mjs.
+  const t = await hwMonitor();
+  const rows = [];
+  if (t.cpu != null) rows.push({ label: "CPU", celsius: t.cpu, warnAt: WARN_C, critAt: CRIT_C });
+  if (t.gpu != null) rows.push({ label: "GPU", celsius: t.gpu, warnAt: WARN_C, critAt: CRIT_C });
+  if (rows.length) return { celsius: rows, throttle: null, ...memory };
+
+  // A zone that has not moved yet is still a zone, so this is an answer with
+  // nothing to draw rather than null. Null would let the sampler give up after
+  // three readings, and a real zone that idled on one value for half a minute
+  // would then never be drawn. thermalSnapshot keeps it off the panel.
+  return zones.length ? { celsius: [], throttle: null, zonesSeen } : null;
+}
+
+/**
+ * Which Windows zones have been seen to change since the deck started, keyed by
+ * the zone's row label: the first value each one read, and whether it has
+ * since read anything else.
+ *
+ * A ZONE IS DRAWN ONLY ONCE IT HAS MOVED. Intel's client reference firmware,
+ * which most laptop BIOSes are built from, ends the package zone's `_TMP` with
+ * "Return a static value if no source is available. Return(3010)" — 27.85°C,
+ * drawn as 28 — and returns a static 3000 when legacy thermal management is
+ * off. Where the zone does have a source it is the embedded controller's "max
+ * platform temperature", never the die. Drawn as it came, a zone stuck on
+ * 3010 reads "Thermal zone 28 °C" on a laptop whose CPU is far hotter, which is
+ * a reading this module invents by passing it on.
+ *
+ * The test is Microsoft's own for a zone: "Each thermal zone must report
+ * actual temperature on the sensor (_TMP). The test runs a varying workload on
+ * the PC, and the temperature is expected to change." Movement rather than a
+ * list of known constants, because a constant is a firmware's choice and the
+ * next one may choose another — and because a firmware that adds 2730 rather
+ * than 2732 reads a real 28°C as 3010, which a list would hide.
+ *
+ * WHAT IT COSTS: a real zone that holds one value from the moment the deck
+ * starts is not drawn until it first changes. Once it has, it stays drawn for
+ * the life of the process however still it then sits — `moved` never goes back.
+ * Compared in whole degrees, because that is what the row shows: a zone whose
+ * row would never change is indistinguishable from a constant to whoever reads
+ * it.
+ */
+function zonesSeenAfter(zones, before = {}) {
+  const seen = { ...before };
+  for (const z of zones) {
+    const prior = seen[z.label];
+    seen[z.label] = prior
+      ? { first: prior.first, moved: prior.moved || z.celsius !== prior.first }
+      : { first: z.celsius, moved: false };
+  }
+  return seen;
+}

package/src/server/thermal-sampler.mjs

@@ -181,12 +181,16 @@ export function lastThermal() {
 }
 
 /** The thermal row /api/system answers: the last reading, with whether the
- *  machine has been held back since the deck started, or null without one. */
+ *  machine has been held back since the deck started, or null without one —
+ *  and null for a reading with nothing to draw, which is a Windows machine
+ *  whose zones have not moved yet (readWindowsThermal). The panel draws a
+ *  section for any object it is handed, and an empty one is not a reading. */
 export function thermalSnapshot() {
   if (!thermal) return null;
-  // The raw kernel count is the sampler's, for the next difference, and not a
-  // reading: the route answers what the panel draws.
-  const { throttleCount, ...shown } = thermal;
+  // The raw kernel count and the zones' first values are the sampler's, for
+  // the next reading, and not readings: the route answers what the panel draws.
+  const { throttleCount, zonesSeen, ...shown } = thermal;
+  if (!shown.celsius?.length && !shown.throttle) return null;
   return { ...shown, heldBack: heldBackSoFar() };
 }