Web & Wire Inspector

Debugging inbound webhooks (from Stripe, Shopify, GitHub, or PayPal) and inspecting API payloads is critical during local development. Commercial tunneling utilities often upload your webhook payloads to cloud servers to display web dashboards.

Explita Tunnel includes a built-in local web inspector that runs directly on your development machine on http://127.0.0.1:39755:

• 100% In-Memory: Traffic payloads are kept exclusively in local RAM and discarded when the CLI process terminates.
• Real-Time Streaming: Live request and response timelines update instantly via Server-Sent Events (SSE).
• Zero-Friction Replay: Replay incoming webhooks locally with a single keystroke or click without having to re-trigger third-party portals.

🖥️ Launching the InspectorCopy Anchor Link

Whenever you start an Explita Tunnel, the inspector starts automatically:

eta 3000

Terminal output:

Explita Tunnel v0.1.0 (CONNECTED)

  Public URL:       https://stark-3000.tunnel.explita.ng
  Forwarding:       http://localhost:3000
  Local Inspector:  http://127.0.0.1:39755
  Fingerprint:      SHA256:4b:92:ef:2a:...

Open http://127.0.0.1:39755 in your browser to view the interactive dashboard.

🔍 Features & CapabilitiesCopy Anchor Link

1. Live Request TimelineCopy Anchor Link

Every incoming request displays in chronological order showing:

• HTTP Method (GET, POST, PUT, DELETE, OPTIONS)
• Path & Query Parameters (/api/webhooks/stripe?source=checkout)
• HTTP Status Code (200 OK, 400 Bad Request, 502 Bad Gateway)
• Latency & Duration (e.g. 24ms)
• Transfer Payload Size (e.g. 1.8 KB)

2. Header & Body InspectionCopy Anchor Link

Click any request to view:

• Request Headers: All headers sent by the client, including verified x-explita-* headers.
• Request Body: Automatically formatted as syntax-highlighted JSON, raw text, or form data.
• Response Headers: Exact headers returned by your local server.
• Response Body: Output returned to the caller.

3. Server-Sent Events (SSE) & WebSocket InspectionCopy Anchor Link

If your application streams Server-Sent Events (e.g. AI LLM token streams) or duplex WebSockets (e.g. Next.js Hot Module Replacement or chat applications), the inspector renders the streaming frames in real time without buffering delays.

🔁 Instant Request ReplayCopy Anchor Link

When debugging a complex webhook (such as a multi-step Stripe checkout completion or GitHub deployment event), re-triggering the event from the external provider's dashboard is tedious.

Explita Tunnel allows instant replay:

Method A: Browser UICopy Anchor Link

Click the Replay button at the top-right of any inspected request card in http://127.0.0.1:39755. The CLI re-transmits the exact method, path, headers, and body to your local development server and captures the new response.

Method B: Terminal HotkeyCopy Anchor Link

While running eta in your terminal, press the r key:

[r] Replaying last request (POST /api/webhooks/stripe) -> 200 OK (18ms)

⌨️ Interactive Terminal ControlsCopy Anchor Link

While the tunnel is running, your terminal responds to the following interactive keyboard shortcuts:

⚙️ Inspector ConfigurationCopy Anchor Link

Change the Inspector PortCopy Anchor Link

If port 39755 is occupied by another service on your machine, specify a custom port:

eta 3000 --inspect 42000

Disable the Inspector (Headless / CI)Copy Anchor Link

When running tunnels inside Docker containers, automated tests, or CI/CD pipelines, disable the inspector to save memory and eliminate unnecessary port bindings:

eta 3000 --no-inspect