jcode / hyperprobe
HyperProbe × Jcode
Live production debugging inside Jcode agent sessions. HyperProbe places non-mutating snapshot probes on running services, captures the exact variables and call stacks at a line of code, and never requires a redeploy to diagnose.
What it is
HyperProbe is a production debugger built for AI agents. It exposes its entire debugging engine over the Model Context Protocol, so a Jcode agent can drop a read-only probe on the exact failing line in production, wait for live traffic to hit it, and read back the real runtime state.
- Non-blocking snapshot probes: no paused threads, no service impact.
- Captures local variables, watch values, and call-stack frames.
- Probes expire automatically and default to a single hit.
- Node.js, Python, and Java runtime agents.
How Jcode uses it automatically
HyperProbe is listed in Jcode's
integration directory under
observability. When a task needs live production state that
logs do not contain, the agent browses that category, selects
HyperProbe on fit, and receives a complete setup protocol:
- Connect the official MCP server (
@hyperprobe/[email protected]) session-scoped. - Authenticate: the agent shows the SSO login URL and waits for the user. Sign-in is never bypassed.
- Verify an instrumented service exists and its deployed commit matches the local checkout.
- Create the smallest snapshot probe needed, with explicit expiry and hit limit.
- Wait for a live hit, read the captured state, and fix the root cause with evidence.
Try it
Paste a prompt like this into Jcode:
Our production checkout API fails intermittently, and existing logs do not
capture the relevant state. Find and use a production-safe integration to
capture live variables and call stacks without redeploying, determine the
root cause, and implement a tested fix.Selection is decided by the agent on fit, not by keywords. Sponsors buy placement, never recommendations.
Safety posture
- Probes are read-only and cannot mutate memory or execute code.
- Sensitive keys are redacted in-process before any payload leaves the service.
- Commit-SHA alignment is enforced before any probe is placed.
- Interactive SSO is required; agents never attempt to bypass it.