Reixo – HTTP client with no-throw Result<T,E> and zero-dep OTel
Yet another HTTP client competing with axios, ky, and got in a saturated market.
A lightweight, local OpenTelemetry trace viewer
Zero-config OTLP listener beats Jaeger for local trace debugging sessions.
Backend developers debugging distributed systems locally
Jaeger UI · Tempo · Honeycomb
During my recent projects with OpenTelemetry, I was looking for a truly practical tool for local development.
I found several existing solutions —some very powerful— but for my day-to-day local use, they were often too heavy, not simple enough to install, or not quick enough to get started with.
So I decided to build my own dedicated tool: otel-gui.
This is not a complete observability suite nor a telemetry backend designed for large-scale production or long-term retention. It's a tool designed for developers who want to debug efficiently locally.
Yet another HTTP client competing with axios, ky, and got in a saturated market.
First semantic cache handling Valkey Search 1.2 divergences without silent breaks.
Wire-protocol parsing means zero code changes to existing OpenTelemetry setups.
Mitmproxy integration shows raw HTTP when LangSmith only shows parsed traces.
Runs with one npx command and immediately surfaces a helpful timeline view with token counts, tool I/O panes and subagent nesting — exactly the sort of visibility you want when an agent goes off the rails. Cleverly reads the local ~/.claude/projects traces so setup is trivial, but its usefulness is limited by being Claude-only and local; add search/aggregation or a team-sharing mode and this jumps up a tier.
Replaces ClickHouse clusters with a single DuckDB container handling 140K events/sec on an M1 Max.