AGENTIC OS
Today’s numbers
Claude Code runs on my machine and sends its telemetry to a hub I built: Collector, Prometheus, Grafana and a small API, five services on Railway behind a Cloudflare Tunnel. The three numbers below come from there while you read this.
- Sessions
- —
- Tokens
- —
- Cost
- —
Every session is its own series: a counter that grows while the session lives, then stops. To add them up I ask the archive for the highest value each series reached in the last twenty five hours. A counter never goes backwards, so that maximum is the session’s total. Asking the Collector instead, which stops exposing a series after a while, looked equivalent and was not: every time it restarted, the sessions that had already ended dropped out of the count. This is not a calendar day, it is roughly the last twenty five hours of activity. As much as these numbers can claim without cheating.
Three aggregate numbers, and nothing else. No prompts, no answers, no free-form queries against the metrics database. Identity never even reaches storage, because the Collector keeps an allow-list on labels: an attribute nobody declared safe is dropped by default, rather than deleted afterwards. That choice came from a measurement, not from a reading. My real email address was arriving as a Prometheus label, and the obvious fix lost data without saying so.
The hub did not answer. I would rather say I do not know than show a zero, which would look like an answer.