2 ms·
Show HN: Hiver – Chrome DevTools for Agents
Hey everyone,
I’m Emmanuel and I built Hiver to help ship reliable AI agents.
I’ve been building agents for a while now. I found that the hardest part isn’t deploying the first version, but iterating on the harness end-to-end (models, skills, memory, system prompts, subagents, tools, environment) to ensure tasks complete successfully and use the least tokens.
To understand why an agent succeeded or failed, we need visibility into everything it did on a computer.
For this reason, Hiver gives agents a computer, so all these interactions are captured with minimal overhead.
Why? Agents want a computer, we just need to make it secure and inspectable.
This is regardless of any SDK or harness. You can build your own harness with open source models all under your own trust boundary if needed.
On the website, you will see a live replay of Claude code with LLM, tools, network, file and browser activity.
I’m interested to learn more about what problems you faced in this space and what solutions you have identified.
- anirud-samala 3mo agoSeems like an interesting product, but does it do similar things as Chrome DevTools?
- blasten 3mo agoYou can see the live replay on hiver.sh. It allows you inspect and trace agent runs: the network panel, file operations, browser navigations, tools, subagents, etc
- xms17189 3mo ago[flagged]