Inspect traffic

LocalCan's traffic inspector shows the HTTP requests flowing through your local domains and Public URLs (tunnels).

Use it to debug webhooks, analyze API calls, and troubleshoot integrations without leaving the app.

Capture

While the desktop app is running, traffic capture is on and every endpoint records by default. Use the Inspect Traffic toggle in the endpoint panel to exclude an endpoint you don't want recorded. When only the daemon runs, for example on Linux or a headless server, capture starts off until you run localcan traffic enable. LocalCan keeps the most recent 250 exchanges in memory only, so captured traffic is cleared when the daemon restarts.

Open the inspector

Click Inspector in the sidebar, or choose Inspect traffic on an endpoint to jump straight to its requests. The All domains picker at the top filters the list to a single domain.

Work with a request

Select a request to see its headers and body next to the response, with JSON prettified and the client IP and the visitor's country flag shown. Replay sends the same request again, straight to the local target it was forwarded to, so the original sender is not involved. It is useful for re-testing webhooks and API calls after a fix. Copy as exports the exchange as Markdown for AI, cURL, HAR, HTTP, or JSON, with an option to redact secrets. Use the arrow keys to move through the list.

A request with status 499 (Client Closed Request) got no answer before the sender hung up: the visitor or webhook sender gave up waiting, or the Public URL's connection closed. Your app may still have answered later, but nobody received that answer. A webhook sender with a short timeout counts this as a failed delivery.

From the CLI and AI agents

The same captured traffic is available from the command line, including exports in the same formats, and to AI agents over MCP.