A confession
I've been using Langfuse and Helicone for the last 6 months. They're great products. Their teams are sharp.
But they don't work for coding agents.
The mismatch
Tool
Langfuse and Helicone are great. But I wanted to see traffic from CLIs that ignore HTTP_PROXY. So I built a local reverse proxy that just logs the loopback.
A confession
I've been using Langfuse and Helicone for the last 6 months. They're great products. Their teams are sharp.
But they don't work for coding agents.
The mismatch
Tool

How I designed a 5,000-line Node.js reverse proxy that captures traffic from Claude Code, Codex, DeepSeek, and 13 other providers…

Two OSS dev tools shipped this month — tracelane (self-contained test-failure replays) and peek (your browser, exposed to your AI…

I recently took on a side project that needed to tap into multiple AI models – GPT-4 for complex...

How I connected Claude, Copilot, and Gemini to a cloud control plane without opening a single port — and why the design matters…

I built Trooper as a fallback proxy. Claude hits quota → falls back to Ollama. Useful but passive. It...

TL;DR: I built Loom, a transparent gRPC proxy that decodes traffic in real-time using Server...