Launching today
Bench for Claude Code
Store, review, and share your Claude Code sessions
127 followers
Store, review, and share your Claude Code sessions
127 followers
Claude Code just opened a PR. But do you really know what it did? By using Bench you can automatically store every session and easily find out what happened. Spot issues at a glance, dig into every tool call and file change, and share the full context with others through a single link: no further context needed. When things go right, embed the history in your PRs. When things go wrong, send the link to a colleague to ask for help. Free, no limits. One prompt to set up on Mac and Linux.
Bench for Claude Code
Hey Product Hunt! 👋
I’m Manuel, co-founder of Silverstream AI. Since 2018, I’ve been working on AI agents across Google, Meta, and Mila. Now I’m building Bench for Claude Code with a small team.
If you use Claude Code a lot and want to store, review, or share its sessions, this tool is for you. Once connected, Bench automatically records and organizes your sessions, letting you inspect and debug them on your own or share them with your team to improve your workflows.
Getting started is simple:
• Go to bench.silverstream.ai and set it up in under a minute on Mac or Linux
• Keep using Claude Code as usual
• Open Bench when you need to understand or share a session
That’s it.
Bench is completely free. We built it for ourselves and now want as many developers as possible to try it and shape it with us.
We’ll be here all day reading and replying to feedback (without using Claude 😂). Would love to hear what you think!
Btw, support for more agents is coming soon, so stay tuned!
I’ve been using Claude Code quite a bit, and I often lose track of what actually happened in a session. This idea of being able to go back and inspect everything feels really useful for me.
Bench for Claude Code
@amard_sonal that's precisely how I am mostly using this product nowadays! It's always pretty insightful to have a second look at all the commands being launched by Claude Code... you would never imagine how often this guy tries to replace my local supabase setup with its own non-working docker containers! :S Through bench, I can understand how it did it and how to remediate, at the very least :)
How deep does it go when tracking tool calls and file changes across a session?
Bench for Claude Code
@hamza_afzal_butt as deep as possible :) The whole goal of Bench is to trace as many details as possible on every action performed by the agent, and then to allow you to review spot the details were looking for easily and quickly! The limit is just on what Claude Code allows us to extract, which is quite a lot anyways! In terms of tool calls, we can extract all the details about the command used to launch the tool, and the "origin" of that call, whether it's the conversation that led the agent there or a subagent run that had a specific goal to reach.
About file changes, it's basically the same thing: we obviously can show the delta, but also why and when the agent took the decision to apply that specific change.
Premarket Bell
How granular is the session tracking? Can you trace decisions step-by-step or it is more of a high level overview?
Bench for Claude Code
@daniel_henry4 the goal of the tool is to allow you to get each specific detail about the whole process: you can follow all actions, subagent calls, and decisions taken during a session, so we try to store data in the most detailed possible way.
Then, of course, this gets quite quickly a lot to manage, especially on longer sessions: imagine having a 200-steps session to troubleshoot, or more, for example! For this reason we are providing a set of tools to also allow you to skim through the steps and highlight the ones you may really care about. Some tools are incredibly simple, such as just grouping steps by type of action, while some other tools are more refined, such as sending warnings on commands that may be potentially concerning. This is the area where we'll focus the most in the future as well, trying to provide as many details as possible, while allowing session analysis to be as quick as possible!
Bababot
I’m curious how detailed the tracking is. If I can really see every tool call and file change clearly, I can imagine using this for debugging more than anything else.
Premarket Bell
How granular is the session tracking? Can you trace decisions step-by-step or it is more of a high level overview?
Serand
Cograts on the launch. I can see this becoming essential for teams using AI agents regularly, especially when debugging or reviewing work.