Request Inspector

LPM CLI starts a local browser inspector alongside an LPM.dev Registry tunnel. It captures the request, the local server's response, status, timing, detected provider, and debugging diagnostics.

The inspector is available on every tunnel plan.

Open the Inspector

lpm tunnel 3000

LPM CLI prints the inspector URL and starts its local web server on an available port. Press o while the standalone tunnel is running to open it.

The same inspector is available when the development server and tunnel start together:

lpm dev --tunnel

Open the inspector URL printed in the startup output. To keep the same local address:

lpm tunnel 3000 --inspect-port 4500

The browser inspector supports:

  • Live request updates without refreshing the page.
  • Request and response headers, bodies, status, and timing.
  • Full-text search across paths, summaries, and body content.
  • Provider, status, and session filters.
  • Named sessions and session-level request history.
  • Failure and signature diagnostics.
  • cURL export for reproducing a request outside the inspector.
  • Single-request replay and ordered replay sequences.

Name a standalone tunnel session when separate webhook tests should remain identifiable:

lpm tunnel 3000 --session "stripe-test"

Replay a Request

Replay sends a captured request back to the local development server. The inspector can use the original request or let you change its method, path, headers, body, and destination port first.

Original request headers are preserved by default, including provider signature headers. host, content-length, and transfer-encoding are regenerated for the new local connection.

Some providers include a timestamp in their signature. Replaying an old request can therefore fail an age check even when the stored body and signature are unchanged.

Sequence replay sends selected requests in order with a configurable delay. A replay result is shown in the inspector but is not recorded as a new inbound tunnel request.

Auto-Acknowledged Requests

When --auto-ack is enabled and the local server is unavailable, the tunnel returns 200 OK to the caller and marks the request as auto-acknowledged:

lpm tunnel 3000 --auto-ack

The request remains in the inspector so you can replay it after the local server restarts.

Local Storage

With the browser inspector enabled, capture history is stored per project:

<project>/.lpm/inspector.db

The SQLite database survives tunnel restarts. Starting another tunnel in the same project makes its stored sessions and requests available to the attached inspector.

The inspector stores at most 10 MB from each request or response body; larger bodies are truncated in the capture database.

Captured headers and bodies can contain credentials, cookies, signatures, and personal data. Keep .lpm/ out of version control and treat inspector.db as sensitive local development data.

Current Terminal-Command Limitation

The browser inspector attached to the running tunnel is the supported workflow for current captures. The standalone lpm tunnel inspect, lpm tunnel log, and lpm tunnel replay commands read a separate legacy store rather than .lpm/inspector.db. lpm tunnel inspect --ui also does not currently reopen this database.

Use the inspector URL printed by lpm tunnel or lpm dev --tunnel. For the exact command behavior, see the LPM CLI tunnel reference.

Continue