Replaying requests

Every captured exchange in the inspector can be re-sent without touching your browser — replay reconstructs the original request and fires it straight at your local app.

How replay works#

Replay rebuilds the request from what was captured — method, URL path and query, headers minus the hop-by-hop ones, and body — and sends it directly to your local app, not back through the edge.

That means replay is deterministic, works even if the tunnel is offline or the edge is unreachable, and tests your app rather than the tunnel itself.

Replaying a request#

Select any HTTP exchange in the request list and press r. The result is entered into the list as a new exchange, marked ↺, so you can compare it against the original. While the replay is in flight, the row shows ~ instead.

Edit and replay#

Press e to open the selected request in an editable form first — method, URL, headers, and body. tab and shift+tab cycle between fields, ctrl+s sends the edited request, and esc discards the edit and closes the form without sending anything.

Limitations#

Bodies are captured up to 256 KiB. A request body larger than that is marked truncated, and a truncated request body cannot be replayed— the bytes genuinely weren't kept, and the UI says so rather than sending a partial body.

WebSocket upgrades aren't replayable either — r and e do nothing when a WSrow is selected, since there's no single request/response pair to reconstruct.