Launched this week
HyperProbe is how backend teams debug production issues they can't reproduce locally. Instead of adding a log line and waiting on a deploy, we let Claude Code, Codex, or Cursor drop read-only probes into a running service and capture the variable state that was never recorded. From there your agent debugs like it has a local repro, closing the bug in one sitting.
Would love to use hyperprobe with go one day! Congratulations though
Hyperprobe
@prashant_patel22 Go is going be launching end of this month Prashant!
One Shot , drop 2 birds - Sentry & Datadog 😉
@shailendra_singh_ht . I zunderstood that this can be helpful for debugging running logic issues, can this be used to diagnose performance bottlenecks or memory leaks as well?
Hyperprobe
@suyash_kr yes we cover Memory OOM and CPU spikes
Context.dev
Excellent!
Hyperprobe
@yahia_bakour3 thanks!
Mailwarm
Congrats on today's launch!!
Read only isn't the same as safe here. The probe still lifts live variable values, so the first question from any security team is what happens when an agent probes the frame holding a card number or a session token, and whether that value ends up in your storage. Zero overhead is doing a lot of work in that sentence too, I'd put a p99 next to it. The 9.5 minutes is the number that actually sells this.
Hyperprobe
@asadmalik901 PII redaction in-process handles this. Our PII bank auto identifies this or you cans set field level redaction yourself
Huge congrats on the launch, team!
Debugging runtime production issues when using coding agents has always felt like the biggest bottleneck. Giving agents dynamic, real variable state right from the IDE instead of digging through logs and constantly redeploying is an absolute game-changer.
Excited to see how HyperProbe transforms AI-assisted workflows. Wishing you guys massive success today! 🙌