Breakpoints
A breakpoint holds a request before it reaches the server, or a response before it reaches the app. You edit it, then send it on.
Add one
Section titled “Add one”- For one URL: right-click a request › Breakpoint… The rule matches that URL with any query string.
- For a host or folder: right-click it in Structure › Breakpoint… The rule matches everything under it.
- From scratch: open the Breakpoints panel from the top bar, click + › Breakpoint, and fill in the URL.
A new breakpoint holds both requests and responses. The panel opens on it so you can change that.
+ also lists the rules of the extensions that are on.

The rule
Section titled “The rule”| Field | |
|---|---|
| Name | What the panel lists the rule as. Without one, it shows the URL. |
| URL | Matched against the whole URL, ignoring case. * stands for any run of characters: https://api.example.com/v2/cart/*. The count beside it is how many captured exchanges it matches. |
| Method | Only this method. Any matches any. |
| Hold | Requests, Responses or both |
The panel lists rules by kind. Each row says what the rule does and how many messages it has held. The switch on a row turns that rule on and off (Space for the chosen one); the switch at the top of the panel turns every rule off, and back on as they were. Right-click a rule to turn it on or off (On), Duplicate it or Delete it. ⋯ in the rule has Duplicate and Delete too, and the × on the row pointed at, and Delete, delete it. Right-click a held message to resume, answer, revert or drop it. Drag the line between the list and the rule to widen the list.
A change applies when you leave the field or press Enter, to every request from then on, on connections already open too.
Rules are saved with the session and come back when zhttp restarts. AI agents can add, change and remove them too, and release what they hold.
When something is held
Section titled “When something is held”-
The Breakpoints panel opens on the held message. The session’s tab light and the dot on the Breakpoints button turn amber. Held messages are listed at the top of the panel, each marked REQ (on its way to the server) or RES (on its way to the app), with how long it has been held. Held by names the rule, or the smart action, that held it.
-
Edit it.
- A request: method, URL, Headers, Query, Cookies, Body.
- A response: status, Headers, Cookies, Body. The arrow beside the status lists the common ones.
Headers are one
name: valueper line. A JSON body has buttons to indent it or strip its white space. Revert puts the message back as it was held. -
Click Resume (Ctrl Enter) to send it as written, or Drop to end the exchange without sending it.
With several held, Resume all (Ctrl Shift Enter) and Drop all at the top of the panel let them all go at once.
Answer a request yourself
Section titled “Answer a request yourself”A held request can be answered from zhttp instead of going to the server. Click Respond…, write the status, headers and body, then click Send response (Ctrl Enter). The app gets your response; the server never hears of the request. Cancel goes back to the request.
Content-Length is set to fit the body you send. A body you didn’t touch goes on as the exact bytes that arrived. A body that can’t be edited as text, such as one whose encoding zhttp couldn’t remove, goes on unchanged.
To hold the messages of a WebSocket, use a WebSocket breakpoint.
A held request appears in the list once it has gone on. The list and AI agents see the exchange as it went: the request as the server got it, the response as the app got it.