mirror of
https://github.com/seanbetts/steam-hardware-watch.git
synced 2026-10-06 03:00:18 +02:00
Initial commit
This commit is contained in:
Sean Betts committed
commit
fbb8c3da72
24 files changed
+2476
No files matched your search
@@ -0,0 +1,304 @@
|
||||
# Steam Hardware Watch
|
||||
|
||||
Agent-oriented monitoring workflow for rumored or upcoming Valve hardware, focused on:
|
||||
|
||||
- `Steam Controller`
|
||||
- `Steam Machine`
|
||||
- `Steam Frame`
|
||||
|
||||
It is designed to be run by a coding agent through the included `SKILL.md`, with scripts that:
|
||||
|
||||
- check `Komodo`, `SteamDB`, `SteamTracking`, and Valve endpoints
|
||||
- save raw artifacts for each run
|
||||
- compare against the previous run
|
||||
- draft a human-readable status update
|
||||
- track visual assets as `discovered`, `retrieved`, or `blocked`
|
||||
|
||||
## What This Is
|
||||
|
||||
This repo is not a generic scraper.
|
||||
|
||||
It is a repeatable evidence-gathering workflow for answering a narrow set of questions:
|
||||
|
||||
- did anything change?
|
||||
- is there a price leak?
|
||||
- is there a release-date leak?
|
||||
- does the controller look ahead of Machine/Frame?
|
||||
- are there new media assets or support documents?
|
||||
|
||||
The normal entry point is the wrapper script:
|
||||
|
||||
```sh
|
||||
scripts/run_watch.sh YYYY-MM-DD /path/to/run-output /path/to/SteamTracking
|
||||
```
|
||||
|
||||
## Repository Layout
|
||||
|
||||
```text
|
||||
steam-hardware-watch/
|
||||
├── SKILL.md
|
||||
├── README.md
|
||||
├── .gitignore
|
||||
├── agents/
|
||||
├── references/
|
||||
├── scripts/
|
||||
└── status/
|
||||
```
|
||||
|
||||
Important directories:
|
||||
|
||||
- `scripts/`: the runnable checks and report builders
|
||||
- `references/`: source map, Komodo notes, evidence rubric
|
||||
- `status/`: seeded baseline answer and run notes
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required:
|
||||
|
||||
- `bash` or `sh`
|
||||
- `curl`
|
||||
- `jq`
|
||||
- `python3`
|
||||
- `node`
|
||||
- `rg`
|
||||
|
||||
Recommended:
|
||||
|
||||
- `playwright-cli`
|
||||
- Google Chrome or Chromium available to Playwright
|
||||
- macOS `open` command with Google Chrome installed for the Komodo background bootstrap helper
|
||||
|
||||
Optional:
|
||||
|
||||
- `ffmpeg` for frame extraction or manual media inspection
|
||||
|
||||
## Quick Start
|
||||
|
||||
1. Clone the repo.
|
||||
2. Make the scripts executable if needed:
|
||||
|
||||
```sh
|
||||
chmod +x scripts/*.sh
|
||||
```
|
||||
|
||||
3. Ensure `SteamTracking` is available locally, for example at:
|
||||
|
||||
```text
|
||||
/tmp/SteamTracking-master
|
||||
```
|
||||
|
||||
4. Run a watch pass:
|
||||
|
||||
```sh
|
||||
scripts/run_watch.sh 2026-04-25 ~/steam_hardware_watch /tmp/SteamTracking-master
|
||||
```
|
||||
|
||||
This creates a dated run folder under `~/steam_hardware_watch/2026-04-25`.
|
||||
|
||||
## Output
|
||||
|
||||
Each run writes:
|
||||
|
||||
- raw API and HTML snapshots
|
||||
- per-source summary files
|
||||
- comparison report versus the previous run when available
|
||||
- `run-summary.md`
|
||||
- `status-draft.md`
|
||||
- visual asset ledgers:
|
||||
- `discovered-visual-assets.tsv`
|
||||
- `retrieved-visual-assets.tsv`
|
||||
- `blocked-visual-assets.tsv`
|
||||
- `manual-asset-urls.txt`
|
||||
|
||||
The main human-readable file is:
|
||||
|
||||
- `RUN_DIR/reports/run-summary.md`
|
||||
|
||||
## Agent Usage
|
||||
|
||||
This repo is meant to be used by coding agents, not only by a human at a shell.
|
||||
|
||||
### Codex
|
||||
|
||||
Install or symlink the repo into your Codex skills directory:
|
||||
|
||||
```sh
|
||||
ln -s "$PWD" ~/.codex/skills/steam-hardware-watch
|
||||
```
|
||||
|
||||
Then ask Codex to use the `steam-hardware-watch` skill.
|
||||
|
||||
### Claude or Other Agents
|
||||
|
||||
Point the agent at this repo and have it:
|
||||
|
||||
1. read `SKILL.md`
|
||||
2. use `scripts/run_watch.sh` as the default entry point
|
||||
3. summarize results from:
|
||||
- `run-summary.md`
|
||||
- `status-draft.md`
|
||||
- any `compare-vs-*.md`
|
||||
|
||||
The agent should treat the scripts as implementation details and present the run summaries to the user.
|
||||
|
||||
## Komodo Caveat
|
||||
|
||||
`Komodo` is the most valuable source and the least reliable one.
|
||||
|
||||
What usually works:
|
||||
|
||||
- public `wp-json` product, section, and media endpoints
|
||||
- still-image asset URLs
|
||||
|
||||
What may fail:
|
||||
|
||||
- video and AVIF asset downloads
|
||||
- some API fetches when Cloudflare blocks automation
|
||||
- optional Playwright fallback if it is pointed at a problematic local browser channel
|
||||
|
||||
The workflow handles this by separating:
|
||||
|
||||
- `discovered`
|
||||
- `retrieved`
|
||||
- `blocked`
|
||||
|
||||
Blocked assets are still reported with direct manual URLs.
|
||||
|
||||
## Optional Komodo Browser Bootstrap
|
||||
|
||||
Use this only when Komodo blocks automated media access and you need the protected files.
|
||||
|
||||
This is intentionally user-local and should never be committed.
|
||||
|
||||
### Preferred Low-Disruption Flow
|
||||
|
||||
Use the bundled helper to launch a dedicated Komodo Chrome instance in the background:
|
||||
|
||||
```sh
|
||||
scripts/bootstrap_komodo.sh
|
||||
```
|
||||
|
||||
This:
|
||||
|
||||
- uses a dedicated profile under `.local/`
|
||||
- launches a separate Chrome instance in the background
|
||||
- exposes a stable CDP endpoint
|
||||
- writes `.local/komodo-env.sh`
|
||||
|
||||
If Komodo needs any manual interaction, switch to that dedicated window when convenient. Otherwise leave it running in the background.
|
||||
|
||||
Then run:
|
||||
|
||||
```sh
|
||||
scripts/run_watch.sh 2026-04-25 ~/steam_hardware_watch /tmp/SteamTracking-master
|
||||
```
|
||||
|
||||
`check_komodo.sh` will automatically pick up `.local/komodo-env.sh` when present.
|
||||
`run_watch.sh` will also auto-close the dedicated Komodo browser at the end unless you set:
|
||||
|
||||
```sh
|
||||
KOMODO_KEEP_BROWSER_OPEN=1
|
||||
```
|
||||
|
||||
When finished:
|
||||
|
||||
```sh
|
||||
scripts/close_komodo.sh
|
||||
```
|
||||
|
||||
That closes only the dedicated Komodo browser/profile, not your normal run output.
|
||||
|
||||
### Manual Playwright Bootstrap
|
||||
|
||||
If you prefer the raw Playwright flow, you can still do it manually.
|
||||
|
||||
1. Open a persistent Playwright browser profile:
|
||||
|
||||
```sh
|
||||
playwright-cli open --persistent --profile ~/.steam-hardware-watch/playwright-profile https://komodostation.com/product/steam-controller_jpy/
|
||||
```
|
||||
|
||||
2. Solve any challenge manually in that browser.
|
||||
|
||||
3. Optionally save storage state:
|
||||
|
||||
```sh
|
||||
playwright-cli state-save ~/.steam-hardware-watch/komodo-state.json
|
||||
```
|
||||
|
||||
4. Reuse that state for later agent runs with environment variables:
|
||||
|
||||
```sh
|
||||
PLAYWRIGHT_PROFILE_DIR=~/.steam-hardware-watch/playwright-profile
|
||||
PLAYWRIGHT_STORAGE_STATE=~/.steam-hardware-watch/komodo-state.json
|
||||
PLAYWRIGHT_REFERER=https://komodostation.com/product/steam-controller_jpy/
|
||||
KOMODO_PLAYWRIGHT_FALLBACK=1
|
||||
```
|
||||
|
||||
The current helper scripts support these variables for Playwright-based fallback fetches.
|
||||
|
||||
Important:
|
||||
|
||||
- the Komodo Playwright fallback is `off` by default
|
||||
- it only runs when `KOMODO_PLAYWRIGHT_FALLBACK=1` is set
|
||||
- by default the Playwright helpers use Playwright's normal Chromium target, not your system Chrome
|
||||
- only set `PLAYWRIGHT_BROWSER_CHANNEL=chrome` if you explicitly want that behavior
|
||||
|
||||
### Stronger Fallback: Live Trusted Browser Attach
|
||||
|
||||
If storage state is not enough for Komodo, use a live trusted browser session instead.
|
||||
|
||||
This is the most reliable path we found for protected Komodo media.
|
||||
|
||||
1. Open the persistent profile and load Komodo successfully:
|
||||
|
||||
```sh
|
||||
playwright-cli open --headed --persistent --profile ~/.steam-hardware-watch/playwright-profile https://komodostation.com/product/steam-controller_jpy/
|
||||
```
|
||||
|
||||
2. Leave that browser running.
|
||||
|
||||
3. Discover the local CDP port for that profile:
|
||||
|
||||
```sh
|
||||
ps aux | rg 'playwright-profile|remote-debugging-port'
|
||||
```
|
||||
|
||||
4. Set:
|
||||
|
||||
```sh
|
||||
PLAYWRIGHT_CDP_ENDPOINT=http://127.0.0.1:PORT
|
||||
KOMODO_PLAYWRIGHT_FALLBACK=1
|
||||
```
|
||||
|
||||
5. Run the watcher again.
|
||||
|
||||
If `PLAYWRIGHT_PROFILE_DIR` is set and a matching Chrome process is already running, `scripts/check_komodo.sh` will try to discover the CDP port automatically and use it instead of reopening the locked profile.
|
||||
|
||||
The helper scripts now support that same live-session route with:
|
||||
|
||||
- `PLAYWRIGHT_CDP_ENDPOINT`
|
||||
- automatic local env loading from `.local/komodo-env.sh`
|
||||
|
||||
## Current Known Limits
|
||||
|
||||
- `Komodo` can block both `curl` and fresh browser automation.
|
||||
- We can currently discover and report blocked media URLs even when we cannot download them automatically.
|
||||
- Exported storage state may still be insufficient for Cloudflare-protected Komodo assets.
|
||||
- Live trusted browser attach is currently the strongest repeatable fallback for protected Komodo media.
|
||||
- The fully non-visual path is not reliable yet; after bootstrap, the working fallback is still a live dedicated browser running in the background.
|
||||
|
||||
## Recommended Workflow
|
||||
|
||||
Normal use:
|
||||
|
||||
1. run `scripts/run_watch.sh`
|
||||
2. read `run-summary.md`
|
||||
3. inspect the comparison report if something changed
|
||||
4. update `status/current.md` and `status/evidence.jsonl` only for material changes
|
||||
|
||||
Escalation:
|
||||
|
||||
1. if Komodo blocks, continue the run
|
||||
2. use `manual-asset-urls.txt` for manual follow-up
|
||||
3. only use the Playwright bootstrap if protected Komodo media is important to the run
|
||||
Reference in new issue
Block a user