Edit and remove breakpoints#

The sidebar lets you select, switch off, and remove a breakpoint, and it counts the requests each one is currently holding.

The sidebar in the Breakpoints sub-tab shows every breakpoint with a toggle next to its name. The count next to Breakpoints at the top shows how many breakpoints are active.

Select a breakpoint#

Select a breakpoint to open it in the editor on the right.

A selected breakpoint also expands into an accordion. The accordion lists the paused requests that the breakpoint holds. Each pending row shows the request method, the URL, and a small icon that shows the side: for Before Request, for After Response.

Switch a breakpoint on or off#

Each row has a switch on the left. Toggle it to enable or disable the breakpoint. A disabled breakpoint pauses no requests, but it stays in the sidebar. You can enable it again without a rebuild of the conditions.

What the sidebar badges mean#

Each breakpoint row shows two labels on the right.

  • A pending count badge, if the breakpoint holds paused requests.
  • The pause-point label: Req, Res, or Both.

Remove a breakpoint#

Each row has a trash icon. Select it to get a confirmation prompt, then GraphDagger removes the breakpoint. Paused requests that the breakpoint holds stay paused. Act on them from the row in the sidebar before you delete the breakpoint.

Fire a breakpoint from a rule#

A rule can also fire a breakpoint with the Trigger Request Breakpoint or Trigger Response Breakpoint action. Use this to combine the match power of a rule (compound conditions, regex, body match) with the interactive pause of a breakpoint.