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).
agentfdr
See why your coding agent looped, drifted, or burned tokens
agentfdr reads the transcripts Claude Code already writes and turns them into a flight recording: per-turn timeline, automatic anomaly flags (loops, error streaks, token burns), live watch mode, plan-usage tracking, and cost estimates. Zero instrumentation, 100% local, MIT.
A few weeks ago I left Claude Code running overnight. In the morning: 2M tokens gone, and the "fix" was editing the same file in a loop for 40 minutes. I had no idea *why* — the evidence had scrolled away.
Then I realized: Claude Code already writes a complete transcript of every session to disk. Nobody was reading it.
agentfdr is the crash investigator's toolkit for those recordings:
🛫 A per-turn timeline of every tool call, the context window's composition, and output tokens 🚨 Automatic anomaly flags: tool loops, error streaks, context bloat, cache thrash 🔍 A dissection panel for any turn — what it saw, what it did, what it cost 📊 Plan usage (5-hour window / weekly) with calibratable budgets 🚦 A CI gate: `agentfdr assert --no-loops --max-tokens 2M`
Zero instrumentation — `npx agentfdr` and you're looking at your own sessions. Nothing leaves your machine. MIT licensed.
Zooming out: working with coding agents is quickly becoming loop engineering — you design and operate the loop your harness runs: what enters the context, which tools fire, when it stops. You can't engineer a loop you can't see. agentfdr wants to be the instrument panel for that discipline.
Fun fact: every screenshot in the gallery is agentfdr dissecting *the session in which Claude Code built agentfdr itself* — flags and all. 🛬
I'd love your feedback — especially which agent CLIs to support next (Codex CLI? Gemini CLI? Aider?).
How does this handle Claude Code sessions that span multiple branches or get interrupted mid-turn? Wondering if the timeline stays coherent or if the anomaly detection gets noisy when there's a context reset.
how does it flag loops in real time without hooking into the actual conversation state
finally something that makes my long claude code sessions actually reviewable, the loop detection caught a stuck tool call i would have missed for sure
does the anomaly detection work offline too, or does it need to ping anywhere to flag loops and token burns? curious how it stays 100% local with that kind of analysis.
Love that you skipped the SDK and just read what Claude Code already writes to disk, zero instrumentation feels like the right call. The per-turn timeline plus automatic loop and token burn flags is exactly what I'd want when something goes sideways mid-session.
How does it actually surface the anomaly flags in real time during a session, and is there any way to set custom thresholds for things like token burn before it pings you?
the "assert --no-loops --max-tokens" gate is the part i'd actually want running unattended, not just the timeline after the fact. question on tuning it though: some loops are legitimate, retrying a failing test until it passes, polling a build, re-reading a file after an edit. how does it tell that apart from a genuinely pathological loop before it kills the run? is the anomaly detection just repetition-count based, or does it look at whether the tool calls are converging toward something (diffs shrinking, errors changing) vs just spinning in place
how does it pick up the transcripts — is there a config to point it at a custom claude code logs directory or does it default to ~/.claude?
finally something that surfaces loop patterns in long claude sessions without making me grep through jsonl files, the live watch mode is genuinely useful when a run starts drifting.
About agentfdr on Product Hunt
“See why your coding agent looped, drifted, or burned tokens”
agentfdr was submitted on Product Hunt and earned 20 upvotes and 24 comments, placing #18 on the daily leaderboard. agentfdr reads the transcripts Claude Code already writes and turns them into a flight recording: per-turn timeline, automatic anomaly flags (loops, error streaks, token burns), live watch mode, plan-usage tracking, and cost estimates. Zero instrumentation, 100% local, MIT.
agentfdr was featured in Open Source (68.6k followers), Developer Tools (515.9k followers), Artificial Intelligence (473.7k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 221.7k products, making this a competitive space to launch in.
Who hunted agentfdr?
agentfdr was hunted by kenta kamihori. 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.
Want to see how agentfdr stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
kenta kamihori
Hi Product Hunt! 👋
A few weeks ago I left Claude Code running overnight. In the morning: 2M tokens gone, and the "fix" was editing the same file in a loop for 40 minutes. I had no idea *why* — the evidence had scrolled away.
Then I realized: Claude Code already writes a complete transcript of every session to disk. Nobody was reading it.
agentfdr is the crash investigator's toolkit for those recordings:
🛫 A per-turn timeline of every tool call, the context window's composition, and output tokens
🚨 Automatic anomaly flags: tool loops, error streaks, context bloat, cache thrash
🔍 A dissection panel for any turn — what it saw, what it did, what it cost
📊 Plan usage (5-hour window / weekly) with calibratable budgets
🚦 A CI gate: `agentfdr assert --no-loops --max-tokens 2M`
Zero instrumentation — `npx agentfdr` and you're looking at your own sessions. Nothing leaves your machine. MIT licensed.
Zooming out: working with coding agents is quickly becoming loop engineering — you design and operate the loop your harness runs: what enters the context, which tools fire, when it stops. You can't engineer a loop you can't see. agentfdr wants to be the instrument panel for that discipline.
Fun fact: every screenshot in the gallery is agentfdr dissecting *the session in which Claude Code built agentfdr itself* — flags and all. 🛬
I'd love your feedback — especially which agent CLIs to support next (Codex CLI? Gemini CLI? Aider?).