Skip to content
Sean Bettsv2.0.0
Back to Building

Steam Hardware Watch

An agent-driven monitoring toolkit that tracks Valve hardware launch signals, compares evidence across sources and turns changes into readable reports.

Sole developer · April–July 2026View on GitHub (opens in a new tab)

Development ended in July; monitoring continued afterwards. The report shown is dated 24 August 2026.

Archived monitoring report, 24 August 2026: 453 visual assets discovered, 396 retrieved and 57 blocked. No public Steam Frame launch-readiness movement was found in the available evidence; some sources were blocked or partial.
In practice

What it does

  1. Checks Komodo, SteamDB, SteamTracking and Valve endpoints for hardware signals
  2. Saves source snapshots and compares each run with the previous one
  3. Produces evidence summaries and human-readable status reports
  4. Tracks discovered, retrieved and blocked visual assets separately
Behind the work

The challenge

Reconciling incomplete signals across multiple sources, handling browser-dependent access and distinguishing meaningful changes from routine metadata updates.

What I learned

The more people discover loopholes in digital systems, the more likely those gaps are to be closed. Komodo eventually shut off the backend access this project had been using. It was a practical reminder that a useful discovery can be temporary, and that tools built around that access need to account for its disappearance.

Built with

  • Python
  • Shell
  • Node.js
  • SteamKit
  • Playwright