coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Heat-monitoring scripts for the desktop tower #35

New issue
Closed
opened 2026-05-23 20:54:31 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-05-23 20:54:31 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-21T06:35:33Z - https://github.com/coilysiren/infrastructure/issues/222

Goal - Scripts to read the kai-desktop-tower's temperature sensors, mirroring the monitoring already running on the kai-server Linux box.

Context: Kai wants the tower's existing heat sensors readable on a schedule, the way the headless Linux box is already monitored. The tower runs Windows 11.

Next:

  • Pick a Windows temp source. LibreHardwareMonitor exposes a JSON HTTP endpoint, well suited to scripting.
  • Script that polls CPU, GPU, and drive temps and logs or surfaces them.
  • Match the shape of the kai-server monitoring so output is consistent across both machines.
_Originally filed by @coilysiren on 2026-05-21T06:35:33Z - [https://github.com/coilysiren/infrastructure/issues/222](https://github.com/coilysiren/infrastructure/issues/222)_ **Goal** - Scripts to read the kai-desktop-tower's temperature sensors, mirroring the monitoring already running on the kai-server Linux box. Context: Kai wants the tower's existing heat sensors readable on a schedule, the way the headless Linux box is already monitored. The tower runs Windows 11. Next: - [ ] Pick a Windows temp source. LibreHardwareMonitor exposes a JSON HTTP endpoint, well suited to scripting. - [ ] Script that polls CPU, GPU, and drive temps and logs or surfaces them. - [ ] Match the shape of the kai-server monitoring so output is consistent across both machines.
coilysiren commented 2026-05-30 05:43:26 +00:00
Author
Owner
Copy link

Iceboxed in the 2026-05-29 backlog burn-down: tower heat-monitoring scripts, hardware-gated hobby. Reopen anytime if it becomes real.

Iceboxed in the 2026-05-29 backlog burn-down: tower heat-monitoring scripts, hardware-gated hobby. Reopen anytime if it becomes real.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/infrastructure#35
No description provided.