> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hyperprobe.co/llms.txt
> Use this file to discover all available pages before exploring further.

# HyperProbe: Production Debugging Without Deployments

> Capture live variable snapshots, inject logs, and trace call stacks in running production code—without pausing execution, redeploying, or changing your source. Get started in under 2 minutes.

You are a senior engineer, so let's skip the marketing speak and talk about last Sunday at 2:00 AM.

## 🚨 The Sunday 2:00 AM Incident

A critical checkout API endpoint is failing for 0.5% of users with an obscure error:
`TypeError: Cannot read properties of undefined (reading 'taxRate')`.

It doesn't happen in your local environment, and it doesn't happen in staging. It only happens under specific production database state conditions.

<Tabs>
  <Tab title="The Painful Old Way (45+ Minutes)">
    1. **Edit Code:** Open your editor and add `console.log('DEBUG USER STATE:', user, order);`
    2. **Push Git Branch:** Commit, push, and open a PR.
    3. **Wait for CI/CD:** Spend 15 minutes waiting for unit tests and build steps to pass.
    4. **Deploy:** Roll out the new Docker image to your Kubernetes cluster.
    5. **Wait for Incident:** Monitor logs, hoping the bug triggers again so you can search CloudWatch/Datadog.
    6. **Discover Gaps:** Realize you logged the `user` but forgot to log the nested `address` object. **Start over from Step 1.**
  </Tab>

  <Tab title="The HyperProbe Way (15 Seconds) ⚡">
    1. **Open VS Code:** Find the failing line in your local repo.
    2. **Place a Snapshot:** Right-click and select **Insert a Snapshot**. (The SDK agent instantly applies a microsecond hook in-process).
    3. **Capture State:** The next time a failing request hits that line, **the exact local variable tree, call stack frames, and watch expressions populate live inside your VS Code sidebar.**
    4. **Inspect & Fix:** You immediately see `address` is an unparsed string instead of an object. You delete the probe and write the fix. **No downtime, no log spam, zero deploys.**
  </Tab>
</Tabs>

***

## 🧠 The AI-Native Edge: Let Your Coding Agent Debug Production

HyperProbe exposes its entire debugging engine via the **Model Context Protocol (MCP)**. This means your local desktop AI assistant (like **Claude Desktop, Cursor, or Windsurf**) can autonomously debug production incidents for you.

<Frame>
  <img src="https://mintcdn.com/hypertest-cee1a811/j0V_sR-3tU1Tj3rh/images/homepage-ai-native.svg?fit=max&auto=format&n=j0V_sR-3tU1Tj3rh&q=85&s=093814a7976195e79559136de7a0055d" alt="AI-Native Production Debugging with MCP" width="800" height="380" data-path="images/homepage-ai-native.svg" />
</Frame>

You can literally ask your AI assistant:

> *"Our user payment processing is throwing exceptions in prod. Go check the live variables of BillingService.ts, isolate the bad payload structure, and tell me how to fix it."*

The AI will:

1. Scan your local codebase to find the file and line.
2. Connect to the HyperProbe Broker using MCP.
3. Automatically inject a Snapshot Probe on the target line.
4. Block on the telemetry queue until a live request hits it.
5. Read the captured state, identify the exact broken parameter, and write the hotfix.

***

## 🔒 Engineered for High-Throughput Production Environments

Attaching a debugger to production sounds terrifying. We built HyperProbe because we were terrified too. Here is why it is completely safe:

<CardGroup cols={2}>
  <Card title="Microsecond Execution Hooks" icon="gauge">
    HyperProbe does **not** pause the event loop or use standard blocking debugging breakpoints. It binds asynchronous listeners directly to the runtime engine (V8 Inspector API for Node.js, runtime Bytecode Manipulation for JVM). Hooks execute and detach in under **15 microseconds**.
  </Card>

  <Card title="Zero-Trust Local Redaction" icon="shield-halved">
    Sensitive properties (`password`, `token`, `cookie`, `creditCard`) are stripped **in-process inside your container** before any payload is compiled or transmitted. Secure credentials never leave your application's memory boundary.
  </Card>

  <Card title="Intelligent Cooldown Shields" icon="temperature-arrow-down">
    The agent continuously monitors event loop lag and heap memory. If it detects more than 15ms of overhead or free memory dropping below 15%, it activates the **cooldown shield**, instantly purging all active probes in-process.
  </Card>

  <Card title="Automatic Expirations & Caps" icon="clock">
    Every probe is created with an explicit lifetime (e.g., 1 hour) and a strict hit limit (snapshots default to `1`). Once met, the probe is permanently uninstalled, ensuring zero residual overhead.
  </Card>
</CardGroup>

***

## Ready to Get Started?

Choose your path and have live production telemetry flowing in under 2 minutes.

<CardGroup cols={3}>
  <Card title="Quickstart Guide" icon="rocket" href="/quickstart">
    Set up the extension and Node/Java SDKs in 120 seconds.
  </Card>

  <Card title="AI MCP Server Setup" icon="microchip" href="/ai-native/mcp-server">
    Connect your coding agent to live debugging tools.
  </Card>

  <Card title="Pillars of Safety" icon="file-shield" href="/guides/safety-guardrails">
    Pass your InfoSec review with our deep safety specifications.
  </Card>
</CardGroup>