Inspect traffic
New in 1.1
Save a session
On this page
Captured traffic lives in memory, and quitting ReqRes clears it. Save a request to keep it, with its response, on disk until you delete it.
Save a request
- Right-click a request in the traffic list.
- Choose Save session.
To save several, select them with ⌘-click or Shift-click, then right-click one of the selected rows. The item names the count, as in Save 3 sessions. If you right-click a row outside the selection, only that row is saved.
A request that is still open, or that ended without its final row, cannot be saved. Save session leaves such rows out, and is unavailable when every row it would save is one. Save the request once it has finished.
Nothing is saved automatically. A session is stored only when you save it, or when an AI agent saves it and you allow it. See Agents and saved sessions.
Find it again
- Choose Window ▸ Saved Sessions, or press ⌘⇧S.
- Click a session in the list. The newest saved is at the top.
- Read its request and response on the right. They use the same tabs as the inspector, described in Inspect a request.
Some kinds of row open differently:
- A saved WebSocket keeps its handshake only, so it has no Messages tab.
- A saved stream keeps its Events tab, and a saved gRPC call its RPC tab.
- A saved relayed connection shows the facts of the connection, as in the inspector.
- A saved request that did not complete shows its banner with the reason. It offers no Exclude or Forget button, because the row comes from an earlier capture.
Each row shows the method, host and path. Below them are the capture and save times, the size, and the note if there is one. A relayed connection shows its endpoint instead, then "Not decrypted", "Not HTTP" or "SSL pinned" with the bytes each way. A request that did not complete shows its outcome glyph in place of the status.
To find a session, type in the "Search host, path, method, app or note" field at the top of the list.
The window loads the newest 500 saved sessions. When you have more, the footer says how many of the total are loaded.
What is stored
A saved session holds the request and response as they were captured, with real values. Headers, cookies, tokens and bodies are stored unmasked. It also keeps the app that made the request and the time it was captured.
- Binary bodies and trailers are stored.
- A body ReqRes kept only in part stays partial, with its notice.
Where it is stored
Saved sessions go into ReqRes's app group container, in the same database as your host filters and rules.
- Settings ▸ Storage ▸ Where it is kept shows the location, with a Show in Finder button.
- Settings ▸ Storage ▸ Saved sessions ▸ Stored shows how many sessions you have and how much space they use.
Delete saved sessions
To delete one:
- Open Window ▸ Saved Sessions.
- Right-click the session and choose Delete Saved Session…. Or select it and press Delete.
- Click Delete in the dialog, which names the request, as in "Delete the saved GET to api.example.com?".
To delete all of them:
- Open Settings ▸ Storage.
- Click Delete All Saved Sessions….
- Confirm in the dialog, which names the count.
ReqRes removes them from disk right away. There is no trash, and a deleted session cannot be restored.
Agents and saved sessions
An AI agent connected to ReqRes can use saved sessions through these tools:
| Tool | What it does |
|---|---|
save_session | Saves a captured request, with an optional note of up to 280 characters. The note shows beside the session in the window. It refuses a request that is still open or that ended without its final row. |
list_saved_sessions | Lists saved sessions, newest first, with their ids and notes. |
get_saved_session | Reads one saved session. A saved stream comes back as its whole body, redacted event by event, without the events or assembled views. |
delete_saved_session | Deletes one saved session. |
save_session and delete_saved_session change data, so ReqRes asks you to approve them, unless you have allowed agent changes. See Approve agent changes.
An agent that reads a saved session gets redacted values, the same as for live traffic. The exception is a host you listed under Settings ▸ MCP ▸ Redaction. See Control what agents see.