History

Every request you send from Composer is logged to a dedicated History tab — not just the request you sent, but the response that came back, so you can review what an endpoint returned without resending it.

Opening History

Click the clock icon in the Collections sidebar header (next to the environment and import icons). History opens as its own tab in the unified tab bar, alongside your session and request tabs — clicking the icon again just switches back to the existing tab instead of opening a second one.

Layout

The tab is a table-and-detail split, same shape as the rest of Probe:

• Table (left) — one row per sent request: Method, URL, Status, Duration, Time. Sorted newest-first by default; click the Time header to flip the order.
• Detail (right) — select a row to see its full Request (headers, params, body) and Response (headers, body) on separate sub-tabs. A response that was truncated when saved (see below) shows a note above the body.

A search field above the table filters rows by method or URL substring as you type.

Loading a past request back into the editor

Right-click a row (or use the Load into Editor button in the detail header) to send that request's captured snapshot back into Composer — method, URL, headers, params, body, and script tabs, exactly as they were when you sent it. If no compose tab is currently open, Probe opens a fresh draft for it; if one is open, it's reused.

Note

Only entries with a captured snapshot can be reloaded. Every entry Probe writes has one — this only matters for very old entries migrated from before this behavior existed.

What's kept, and for how long

• Up to 200 requests are kept, oldest evicted first when the log is full.
• Each entry's response body is capped at 256 KB when saved — a larger body is truncated and flagged, and the truncation note appears above the body in the Response sub-tab.
• History is a permanent file on disk (~/.probe/compose_history.json, not SharedPreferences), so it survives app restarts.
• Delete a single entry from its row's context menu, or clear the whole log from the table.

Tip

History captures the same last response that Composer already keeps per request (see Composer Overview) — the difference is History is an append-only log across every send, while the per-request "last response" is overwritten each time you resend the same request.

Related

Composer Overview Where Send lives and how responses are captured.

Collections Save a request from History permanently instead of just reloading it once.