HyperProbe: Agents that do read-only debugging in prod
HyperProbe lets a coding agent place bounded, read-only probes in a live Node, Python, or Java service, then capture variable snapshots across the call stack when real traffic reaches the line. It aims to replace the slow add-a-log, redeploy, reproduce cycle—especially for silent logic failures that ordinary exception and trace systems never record.
The design is deliberately constrained: in-process redaction, no writes, hit/expiry/token-bucket budgets, size and depth caps, network limits, and automatic suspension when probe overhead exceeds a threshold. The team reports roughly 7–10 ms active-probe overhead in Node, 4–9 ms in Python, and 1–2 ms in Java; idle probes are intended to have negligible cost. You can self-host the server, broker, and database.
HN commenters liked the hypothesis-driven debugging model but raised the important counterpoints: mature observability already handles many failures, a single snapshot can mislead, and audit trails are still on the roadmap. The authors say the agent should treat snapshots as evidence for testing hypotheses, not as an infallible diagnosis.