This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Replay Doctor
Find the turn your prompt cache broke, and what it cost
See what your AI agent actually spent. Replay reads the transcripts Claude Code and OpenAI Codex already keep on disk, reconstructs token usage and cache behavior, and names the turn a prompt cache broke and what it cost. It reproduces the provider's own cache reads before reporting anything, and prints NOT MEASURED where the evidence is absent instead of guessing. Built to measure GPT-6 Astra. Not measured yet. Single Go binary, zero third-party dependencies, no account.
Hey Product Hunt! I'm Daniel, founder of Red Robot K.K. in Tokyo. I built Replay because I got tired of opening my provider dashboard and seeing unexplained API bill spikes with zero error logs to account for them.
The Problem:
When you run local coding agents like Claude Code and OpenAI Codex, a client re-render or a long idle gap can silently break your prompt cache. When it breaks, providers re-bill your conversation history at cold write prices instead of cached read prices. On my own agent runs, 4% of my bill was tokens billed a second time. Measured 4.18% on 123 sessions, read 2026-09-17.
How Replay Fixes It:
Replay is a local Go CLI with zero third-party dependencies. It reads your transcript logs off your disk, replays them turn by turn against provider caching rules taken from published vendor documentation with the date each was read, and names the turn the money went.
Zero telemetry: no accounts, no cloud tracking. Four network requests exist and each is a command you type. One exception is disclosed: replay burn probes 127.0.0.1 for a local Ollama on every run.
Privacy: it never stores your raw message text. Only hashed structural details, block sizes and tool names.
On Astra, the honest version. Built to measure Astra. Not measured yet. Replay already reads the rollout format Astra writes and carries the documented GPT-6 Astra pricing and cache rules. What it has never read is an Astra turn carrying token counts, because generating that traffic costs money this project does not have. Where that figure would go, Replay prints NOT MEASURED rather than estimating, and so does the site. Contest credits would fund the first real Astra runs, and those measurements would be published with their dates and provenance like every other figure.
Run the installer and tell me what your re-billed percentage looks like. I'll be in the comments all day.
Grok lands by the end of this week. The reader is written and runs on my own machine against 106 Grok sessions; it is held out of this release because its refusal paths do not yet have tests observing them, and a reader whose safety checks are unverified is not one I want to ship into a tool that exists to refuse what it cannot measure.
About Replay Doctor on Product Hunt
“Find the turn your prompt cache broke, and what it cost”
Replay Doctor was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #101 on the daily leaderboard. See what your AI agent actually spent. Replay reads the transcripts Claude Code and OpenAI Codex already keep on disk, reconstructs token usage and cache behavior, and names the turn a prompt cache broke and what it cost. It reproduces the provider's own cache reads before reporting anything, and prints NOT MEASURED where the evidence is absent instead of guessing. Built to measure GPT-6 Astra. Not measured yet. Single Go binary, zero third-party dependencies, no account.
On the analytics side, Replay Doctor competes within Software Engineering, Artificial Intelligence, GitHub and OpenAI Day — topics that collectively have 563.6k followers on Product Hunt. The dashboard above tracks how Replay Doctor performed against the three products that launched closest to it on the same day.
Who hunted Replay Doctor?
Replay Doctor was hunted by Daniel Saito. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Replay Doctor including community comment highlights and product details, visit the product overview.
Daniel Saito
Hey Product Hunt! I'm Daniel, founder of Red Robot K.K. in Tokyo. I built Replay because I got tired of opening my provider dashboard and seeing unexplained API bill spikes with zero error logs to account for them.
The Problem:
When you run local coding agents like Claude Code and OpenAI Codex, a client re-render or a long idle gap can silently break your prompt cache. When it breaks, providers re-bill your conversation history at cold write prices instead of cached read prices. On my own agent runs, 4% of my bill was tokens billed a second time. Measured 4.18% on 123 sessions, read 2026-09-17.
How Replay Fixes It:
Replay is a local Go CLI with zero third-party dependencies. It reads your transcript logs off your disk, replays them turn by turn against provider caching rules taken from published vendor documentation with the date each was read, and names the turn the money went.
Zero telemetry: no accounts, no cloud tracking. Four network requests exist and each is a command you type. One exception is disclosed: replay burn probes 127.0.0.1 for a local Ollama on every run.
Privacy: it never stores your raw message text. Only hashed structural details, block sizes and tool names.
On Astra, the honest version. Built to measure Astra. Not measured yet. Replay already reads the rollout format Astra writes and carries the documented GPT-6 Astra pricing and cache rules. What it has never read is an Astra turn carrying token counts, because generating that traffic costs money this project does not have. Where that figure would go, Replay prints NOT MEASURED rather than estimating, and so does the site. Contest credits would fund the first real Astra runs, and those measurements would be published with their dates and provenance like every other figure.
Run the installer and tell me what your re-billed percentage looks like. I'll be in the comments all day.
Grok lands by the end of this week. The reader is written and runs on my own machine against 106 Grok sessions; it is held out of this release because its refusal paths do not yet have tests observing them, and a reader whose safety checks are unverified is not one I want to ship into a tool that exists to refuse what it cannot measure.