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
HarnessForge Studio
Replay an AI agent trace offline and find where it broke
Import a recorded agent trace (JSON/JSONL), replay it as a timeline, see loops, retries, failed tools and token growth flagged, compare the fixed run against the broken one, and export a report with secrets masked. One offline HTML file, $49 once.
Hi all. I built this because I kept losing evenings scrolling through agent traces trying to work out where a run went sideways. Forty tool calls, half of them retries that look identical, and the token count quietly doubling somewhere in the middle. Reading raw JSONL for that is miserable.
So HarnessForge loads the trace and shows it as a timeline. It pairs each tool call with its result, flags the repeats, loops, failed calls and token spikes, and tells you why it flagged them. You can load the fixed run next to the broken one and see what changed. Then export the whole thing as Markdown, JSON, CSV or text with any API keys it spotted masked out.
It's one HTML file. Runs in Chrome or Edge on your desktop, nothing gets uploaded, no account.
Things it doesn't do, so nobody's surprised: it doesn't run or predict a model, it just reads what was recorded. The warnings are heuristics, not answers. And the secret masking is pattern-based, so check an export before you share it.
About HarnessForge Studio on Product Hunt
“Replay an AI agent trace offline and find where it broke”
HarnessForge Studio was submitted on Product Hunt and earned 0 upvotes and 2 comments, placing #274 on the daily leaderboard. Import a recorded agent trace (JSON/JSONL), replay it as a timeline, see loops, retries, failed tools and token growth flagged, compare the fixed run against the broken one, and export a report with secrets masked. One offline HTML file, $49 once.
On the analytics side, HarnessForge Studio competes within Productivity, Developer Tools and Artificial Intelligence — topics that collectively have 1.7M followers on Product Hunt. The dashboard above tracks how HarnessForge Studio performed against the three products that launched closest to it on the same day.
Who hunted HarnessForge Studio?
HarnessForge Studio was hunted by Leandri Nagel. 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 HarnessForge Studio including community comment highlights and product details, visit the product overview.
Hi all. I built this because I kept losing evenings scrolling through agent traces trying to work out where a run went sideways. Forty tool calls, half of them retries that look identical, and the token count quietly doubling somewhere in the middle. Reading raw JSONL for that is miserable.
So HarnessForge loads the trace and shows it as a timeline. It pairs each tool call with its result, flags the repeats, loops, failed calls and token spikes, and tells you why it flagged them. You can load the fixed run next to the broken one and see what changed. Then export the whole thing as Markdown, JSON, CSV or text with any API keys it spotted masked out.
It's one HTML file. Runs in Chrome or Edge on your desktop, nothing gets uploaded, no account.
Things it doesn't do, so nobody's surprised: it doesn't run or predict a model, it just reads what was recorded. The warnings are heuristics, not answers. And the secret masking is pattern-based, so check an export before you share it.