PipeHero dashboard showing a live tunnel and captured webhook requests

PipeHero: the webhook tool I built because I needed it

I’ve been building GitArena for a while now, and a good chunk of it lives and dies by webhooks. GitHub sends PR events, other services send their own, and all of it needs to land on my machine while I’m actually building the thing that reacts to it. That meant a tunnel to localhost was always running somewhere in a terminal I forgot about. The annoying part wasn’t the tunnel itself. It was everything around it: the URL rotates, so I go re-paste it into GitHub’s webhook settings. I want to see the payload that just came in, so I dig through a provider’s dashboard or add a print() I’ll forget to remove. I want to re-send the same event without waiting for GitHub to fire it again, and that’s not really an option unless I pay for it. Multiply that by every provider GitArena talks to, and it stops being a minor annoyance and starts being the thing that breaks my flow every time I sit down to work. ...

15 de julio de 2026 · 4 min · Alberto Paparelli
Claude Code tool usage breakdown: Bash 48%, Read 30%, Edit 13%

Teaching Claude about your codebase, once, for everyone

I’ve been building a CLI tool to monitor Claude Code usage: tokens consumed, costs per session, tool breakdown by volume. The cost numbers weren’t surprising. But the tool breakdown was. 1 2 3 4 5 6 7 Tools by volume (last 7 days, all projects) ------------------------------------------------ Bash ████████████████████ 427 (48%) Read █████████████ 270 (30%) Edit █████ 112 (13%) Write █ 30 ( 3%) Agent █ 16 ( 2%) 30% of all tool calls are Read operations. Not writing code, not running tests. Just Claude opening files to understand how the codebase is structured before it can help with anything. Context it builds up over the session and loses completely when the session ends. ...

9 de junio de 2026 · 4 min · Alberto Paparelli