Breakpoints & resend

Pause a request or response, edit it live, and replay any captured request.

Breakpoints pause a matching request or response mid-flight so you can edit the raw HTTP before it continues. Resend replays any captured request. Both let you change traffic instead of only watching it.

Heads up: Breakpoints fire across every capture source — the web proxy-server (PAC / proxy host), the CDP connector, and iOS in both VPN and PAC modes. iOS VPN-mode (packet-tunnel) traffic runs the same breakpoint cycle on-device, inside the tunnel extension.

Setting breakpoints

Open the Breakpoints page from the settings nav.

  1. Add Request patterns (pause an outgoing request before it reaches the upstream server) and/or Response patterns (pause an incoming response before it reaches the client). Patterns are simple host + path wildcards, for example *.api.example.com/v1/*. Click Save patterns to push them to the proxy.
  2. Or hit Pause all requests — a one-click catch-all (*) that pauses every outgoing request with no pattern needed. Toggle Resume all to revert.

Per-device patterns can be set under Devices → ‹device› → Breakpoints; the global patterns are the fallback.

Editing a paused request

When traffic matches, it appears under Live pauses. Pick it and edit the raw HTTP in the textarea — method, path, headers, and body. Content-Length is recomputed automatically; Host is editable but won't reroute the request. Then:

  • Continue — let it proceed, with or without your edits.
  • Abort — drop the request entirely.
  • Reset — revert your edits back to the captured original.

A live status pill shows the subscription health.

How it travels

Your Continue/Abort decision is published over the proxy-control Realtime channel to the device that owns the paused request. If nothing decides within 60 seconds, the pause times out on its own so a forgotten breakpoint never wedges traffic permanently.

matchLive pause(60s)ContinueAbort

Resending a request

From the detail panel's action bar on any captured request:

  • Resend re-issues the request as-is. The device (or proxy-server) replays it and stamps a resent marker, so the new capture shows up in the feed tagged resent.
  • Edit & Resend opens a modal to tweak the method, URL, headers, or body first, then replays it.

Any {{VAR}} placeholders in the URL, headers, or body are resolved against the device's environment variables just before the request leaves — so you can replay a call with a fresh token without pasting the secret.

Use the Resent filter in the feed to isolate replayed requests from originals.

Tip: Combine breakpoints and resend to iterate on a request: pause it, copy it, then Edit & Resend variations until you get the response you're after.