Breakpoints

Breakpoints pause a matching request or response mid-flight so you can inspect and edit it before it continues — like a debugger breakpoint, but for HTTP traffic.

Setting a rule

Open Breakpoint Manager (⌘4 or the toolbar pause icon) and add a rule matching on domain, path, or method, scoped to the request phase, response phase, or both. Rules can be toggled on/off individually without deleting them.

When a request pauses

A banner appears over the main window as soon as a matching request hits the rule. Click it to open the Paused Breakpoints dialog:

• Left: list of every currently-paused request (there can be more than one queued at once), each with a live countdown — an unresolved breakpoint auto-forwards after 120 seconds so a forgotten pause never blocks traffic indefinitely.
• Right: the selected request’s editor — URL, Headers, Cookies, Body, and Raw tabs, all editable.

Resolving a paused request

Three actions, always available:

• Resume — forward the request (with whatever edits you made) on to its destination.
• Drop — close the connection silently, no response sent.
• Force Fail — respond immediately with a status code you pick (e.g. 500, 403) without ever reaching the real server — useful for testing how a client handles specific error responses.

WebSocket frames

Breakpoints also work on individual WebSocket frames via Live Attach on an open socket — pause a frame, edit its payload, resume or drop. See WebSocket for the frame-level UI.