Show HN: StackReplay – analyze and replay your AI coding history locally
Private workload analyzerYour AI coding history, measured.Claude Code, Codex and Command Code already record every model call. StackReplay reads that history in your browser and shows what the work is worth at published API prices, what drives it and when it gets heavy. One developer's Codex history, aggregates only.
- ▪Private workload analyzerYour AI coding history, measured.Claude Code, Codex and Command Code already record every model call.
- ▪StackReplay reads that history in your browser and shows what the work is worth at published API prices, what drives it and when it gets heavy.
- ▪One developer's Codex history, aggregates only.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,419 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | StackReplay |
| Canonical URL | https://stackreplay.com |
| Publication time | Fri, 25 Sep 2026 12:12:27 +0000 |
| Retrieval time | 2026-09-25T12:25:32.341Z |
| Last seen | 2026-09-25T12:25:32.341Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 9o3gMiofNvdq · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Private workload analyzerYour AI coding history, measured.Claude Code, Codex and Command Code already record every model call. StackReplay reads that history in your browser and shows what the work is worth at published API prices, what drives it and when it gets heavy. Then replay it against another plan or API to see where the allowance would have run out.Scan your AI historyCompare plans01 / Observed workloadAnonymized real workloadHistory window34 daysAug 21 to Sep 23, 2026Events25,788recorded model callsKnown tokens3.12B97.7% cache readsSessions14634 projects · 27 active daysModel mixGPT-5.6 Sol64%GPT-6 Sol18%GPT-6 Astra18%+2 more<1%Observed, not generated. One developer's Codex history, aggregates only.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at StackReplay.
Discussion
0 commentsMore from StackReplay
