Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Real-time dashboard for Claude Code agent teams

github.com

Post reply on HN
Print view View original

21–30 of 54 posts

Re: Show HN: Real-time dashboard for Claude Code agent teams

#21

Post by LuxBennu »

simple10 wrote: post #13
ivaivanova wrote: post #9

Earlier quoted context omitted.

The hooks approach seems much cleaner for real-time. Did you run into any issues with the blocking hooks degrading performance before you switched to background?

Sort of. It wasn't really noticeable until I did an intentional audit of performance, then noticed the speed improvements. Node has a 30-50ms cold start overhead. Then there's overhead in the hook script to read local config files, make http request to server, and check for callbacks. In practice, this was about 50-60ms per hook. The background hook shim reduces latency to around 3-5ms (10x improvement). It was notic…

[dead]

Re: Show HN: Real-time dashboard for Claude Code agent teams

#23

Post by kami23 »

petcat wrote: post #8

Are you guys spending hundreds (or thousands) of dollars a day on Claude tokens? Holy crap. I can't get more than one or two agents to do anything useful for very long before I'm hitting my usage limits.

I'm in a great situation where I've been piloting Claude for the company among a small group of others. I've been obsessed with pushing the limits of how many sessions and agents I can working at a time. We threw some work at Gas Town and another Orchestrator but they felt too rigid and opinionated for my liking. But I'm biased, I want to make my own eventually.

When I go home to my $20 plan I am sad and annoyed but I don't want to put more in for what is a good enough for me to work a bit at a time, a good pomodoro timer for me personally.

Something like this is perfect for some of the issues that I've wanted to solve as a command and control tool with malleable visuals.

OP: This is cool, thank you for sharing.

Re: Show HN: Real-time dashboard for Claude Code agent teams

#24

Post by kami23 »

I tried using hooks for setting up my DIYed version of what channels is now in Claude. I had Claude writing them and not really looking at the results cause the vibes are strong. It struggled with odd behaviors around them. Nice to see some of the possible reasons, I ended up killing that branch of work so I never figured out exactly what was happening.

Now I'm regretting not going deeper on these. This is the type of interface that I think will be perfect for some things I want to demonstrate to a greater audience.

Now that we have the actual internals I have so many things I want to dig through.

Re: Show HN: Real-time dashboard for Claude Code agent teams

#25

Post by simple10 »

kami23 wrote: post #24

I tried using hooks for setting up my DIYed version of what channels is now in Claude. I had Claude writing them and not really looking at the results cause the vibes are strong. It struggled with odd behaviors around them. Nice to see some of the possible reasons, I ended up killing that branch of work so I never figured out exactly what was happening. Now I'm regretting not going deeper on these. This is the type o…

Right on. Good luck! You might also want to play around with https://github.com/simple10/agent-super-spy if you want to see the raw prompts claude is sending. It was really helpful for me to see the system prompts and how tool calls and message threads are handled.

Re: Show HN: Real-time dashboard for Claude Code agent teams

#28

Post by LeoStehlik »

This is what I've been missing running multi-agent ops through OpenClaw.

The opacity problem is the one I hit hard: when a coordinator spawns 3-4 agents in parallel (builder, reviewer, tester, each with their own tool calls), the only visibility you have is what they choose to report back. Which is often sanitised and … dangerously optimistic.

The role separation / independent verification structure I run helps catch bad outputs, but it doesn't give me the live timeline of HOW an agent got to a conclusion. That's why I find this genuinely useful.

Noticed OpenClaw is already on the roadmap - had my hands tingling to fork and adapt it. Starring it for now and added to my watchlist. The hook architecture should translate … OpenClaw fires session events that could feed the same pipeline. Looking forward to seeing that happen.

Re: Show HN: Real-time dashboard for Claude Code agent teams

#30

Post by justin_vin »

LeoStehlik wrote: post #28

This is what I've been missing running multi-agent ops through OpenClaw. The opacity problem is the one I hit hard: when a coordinator spawns 3-4 agents in parallel (builder, reviewer, tester, each with their own tool calls), the only visibility you have is what they choose to report back. Which is often sanitised and … dangerously optimistic. The role separation / independent verification structure I run helps catch…

[flagged]
Post reply on HN