What it covers
-
01
Usage and host health
OpenRouter usage is grouped by app and model, with daily totals and anomaly notes. Host cards show disk, RAM and load against a threshold, so a machine that is over the line is visible without SSH.
OpenRouter usage by app, with daily totals and model notes. App names are blurred. 
Host health: disk, RAM and load against a threshold. Names are blurred. -
02
Knowledge vault
Raw inputs — URLs, articles, markdown — are archived, then compiled into wiki notes with linked concepts. The page shows recent updates and an ingest prompt; the same folder can be opened in a local editor.
Knowledge vault: raw inputs compiled into wiki notes. Source URLs are blurred. -
03
Paper ingest
arXiv metadata is ingested on a schedule and mixed with Hugging Face Papers upvotes. Filters cover topic, search, sort and paging. PDFs can be cached on first open.
Paper list with topic filters, search, sort and Hugging Face upvote mix. Topic labels are blurred. -
04
BTC 5-minute desk
A window aligned to Polymarket btc-updown-5m shows the countdown, a price-to-beat reference, Binance last and REST snapshots. Charts sit on the same page as Chainlink settlement notes.
BTC 5-minute desk: session clock, price-to-beat and Binance last. 
Polymarket Up/Down and Binance last on a shared 15-minute axis. -
05
Monitors and cron
Page monitors watch URLs on an interval and can notify on Telegram when content or status changes. The cron list shows installed jobs, last exit and log age — keys and chat IDs stay off the published screens.
Page monitor: add a URL, set an interval, read recent diffs. Token and chat ID are blurred. 
Cron list: installed jobs, last exit and log age. Job names are blurred.
The problem
Model bills, host checks, research notes, paper feeds and page watches arrived in different tabs and cron logs. Confirming that a job had run, that a host was over a threshold, or that a paper had been ingested meant opening several tools.
How it was built
The console is a FastAPI app with Jinja2 templates and HTMX partials, stored in local SQLite. Crontab and in-app workers pull model usage, host snapshots, paper feeds, social backups and Telegram alerts. The knowledge vault archives raw URL and markdown ingest, then compiles it into a wiki. The BTC desk aligns prediction-market five-minute windows with spot and settlement feeds.
What changed
Operators review usage, hosts, papers and monitors in one system. What was ingested, compiled, scheduled and flagged sits on the same record, instead of in a set of logs.