Bench for Claude Code
Store, review, and share your Claude Code sessions
599 followers
Store, review, and share your Claude Code sessions
599 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.
heyy does this work only with claude? or i can use it with gemini, codex too?
@janhavidadhania Hey Janhavi! We are currently only supporting Claude Code. However, support for other agents is high priority in our feature list - so stay tuned! You can subscribe at bench.silverstream.ai to get notified when support for future agents will be available!
Hey folks! I’m Simone, Co-founder and CTO of Silverstream AI.
Really happy to be launching this today. I’m excited to share it, and very curious to hear your feedback!
One habit we’ve introduced across the team is linking Bench sessions in PRs whenever Claude Code was involved in creating or debugging a change. It gives reviewers a lot more context on how a bug was found and fixed, instead of just showing the final diff.
That’s been one of the most useful workflows for us, and I’d recommend it to other teams using Claude Code too.
I’m also using Bench in a research setting, where session data helps generate detailed methodology reports showing how results were obtained. I’m already finding it useful, and I think there’s a lot more to unlock there!
Looking forward to your thoughts. I want to make Bench as useful for other devs as it's been so far for us, and your input really matters!
The session sharing feature is what makes this stand out. I've lost count of how many times I've wanted to show a teammate "hey look what Claude did here" and had to resort to copy-pasting terminal output into Slack.
Being able to just send a link to a full session with context would save so much back and forth. Especially useful for code reviews where you want to show the AI's reasoning, not just the final diff.
@mihir_kanzariya Exactly, that's one of the main reasons we created Bench! I hope we have effectively solved your issue. When you have the chance to try, please let me know how the experience was, and how we can improve the product!
Hey Product Hunt! I'm Omar, Founding Researcher at Silverstream AI.
We originally built Bench as an internal tool to make debugging our own agents less painful, and it's become something I reach for every day.
My favorite part? The high-level run overview. When an agent run has hundreds of steps, being able to scan the whole thing at a glance and immediately spot where something went wrong is a huge time-saver. From there, I can zoom in all the way down to the model's reasoning traces at the exact step where things broke, which makes a real difference when you're trying to understand why an agent made a certain decision, not just what it did.
As we kept adding features, we realized Bench had become too useful to keep to ourselves, so here we are! 🚀
We're starting with Claude Code, but support for more agents is on the way. Give it a try and let us know what you think!
Nice.
Most people don’t need logs.
They need to understand why the agent made a bad decision and how to prevent it next time.
@ion_simion_bajinaru Exactly. Most people do not like logs: they have to use them to understand what the agent did, why it went wrong, and what to change so it does better next time. Bench is meant to make that whole process easier on your brain.
Hi everyone! 👋 I’m Giulio, co-founder and COO at Silverstream AI.
It feels like we’re all trying to buy back time these days. There’s always more to do, and never enough hours. That’s why I really think tools like Bench for Claude Code matter.
Agents are getting better fast, which means longer and more complex sessions. Hopefully more reliable too. But even as trust increases, I don’t think we’ll ever fully give up control. We’ll always want the option to see what they’re doing, as long as it doesn’t slow us down.
That’s exactly what we’re building Bench for.
If you try it out, I’d really appreciate your feedback. It’ll help us shape our product in the right direction.
Free with no limits is great but I'm curious about the longer-term model here. Storing full session histories with every tool call and file diff is not cheap at any meaningful scale, especially for teams running Claude Code across multiple engineers all day. Is the plan to eventually charge for storage, or is this more of a funnel into a paid product you're building alongside this?