Sessions

A Session in Probe is a saved snapshot of captured traffic — every request and response Probe recorded between Start and Save. Sessions live in browser-style tabs at the top of the log table. One tab is always the recording tab where new traffic lands; the others are read-only saved sessions you’ve opened for review.

Sessions are how you keep traffic across app restarts, how you bookmark a reproduction of a bug, and how you share captures with teammates.

Tabs

The tab bar sits above the log table. Each tab holds its own captured entries — switching tabs swaps the entire log table content, the Detail panel, and the active filter.

Tab basics:

New tab — click + at the right of the tab bar, or View → New Tab. The new tab becomes the recording tab; new traffic flows into it.
Switch tabs — click a tab. The keyboard shortcut for next/previous tabs is in the View menu.
Rename — double-click a tab name.
Close — click the × on a tab. If it has unsaved changes (the dirty marker is showing), Probe asks before discarding.
Reorder — drag tabs to rearrange.
Right-click a tab for Set as Recording, Save Session (when the recording tab is dirty), Duplicate Tab, Close Tab, and Close Other Tabs.

The recording tab is the one currently capturing live traffic. Only one tab is recording at a time. New tabs become the recording tab automatically; saved tabs are always read-only.

Dirty marker

If the recording tab has captured traffic since its last save, an asterisk appears next to the title (Untitled *). The asterisk clears when you save, and re-appears as soon as new traffic arrives.

Saving a session

Press Cmd+S on macOS or Ctrl+S on Windows. Several things happen at once:

The current tab is renamed (Probe prompts for a name on first save).
The tab becomes read-only — no new traffic flows into it.
The dirty * marker clears.
A fresh recording tab opens automatically, so capture continues without a gap.

Saved sessions are stored locally under Probe’s data directory — ~/.probe/sessions/ on macOS, %USERPROFILE%\.probe\sessions\ on Windows — as JSON keyed by session id. To hand a session to a teammate, export it from the Session Manager and you’ll get a .pro file.

Session Manager

Open it from View → Sessions. The Session Manager lists every saved session on this machine and lets you:

Open — load a session into a new tab.
Rename — change the display name.
Export — write the session to a .pro file anywhere on disk.
Delete — remove a saved session. Tabs already open with that session stay open until closed.

The header has an Import button for picking a .pro file from disk and opening it as a new read-only tab.

File format

Probe sessions use the .pro extension. Files contain the full request and response data — headers, query strings, bodies — for every entry in the saved tab.

Older files with the legacy .gmp extension are accepted on import (Probe was once “Guide MITM Proxy”). Probe only writes .pro for new exports.

# macOS — export the session from the Session Manager,
# then share the resulting .pro file
scp ~/Downloads/login-bug.pro teammate@host:/tmp/

A .pro file is everything someone needs to see what you saw:

Reproduce the bug in Probe; press Cmd/Ctrl+S to save.
View → Sessions, find the saved entry, click Export, pick a destination.
Send the .pro file (chat, email, attachment).
The recipient opens Probe → header Import button (or View → Sessions → Import), selects the file. The session opens as a new read-only tab.

Bodies, headers, timing, and connection data all travel with the file, so a teammate can dig into the Detail panel, search across headers and bodies, and replay individual requests in the Composer — without ever needing to re-run your scenario.

Multi-select traffic actions

You can act on more than one log row at a time. Select multiple rows in the log table:

Cmd/Ctrl-click to add or remove individual rows from the selection.
Shift-click to select a contiguous range.

Right-click anywhere in the selection for the multi-select menu:

Save N to Saved Folder — copies the selected entries into one of the Saved folders in the sidebar.
Save N to Collection — adds each selected request to a Composer collection (you pick which collection and folder). This is the bridge between captured live traffic and the Composer: capture a flow, hand the requests to the Composer, and iterate on them as editable, repeatable calls.
Export N requests — write the selection out (cURL, raw HTTP, .pro, etc.).
Compare (when exactly two rows are selected) — opens the diff view.
Clear selection — drop the multi-select.

The selection clears once an action completes, so you can scan a long capture for the few rows that matter, ship them to a collection, and keep going.

Quit confirmation

If the app has dirty tabs (unsaved capture) when you quit, Probe shows a confirmation dialog asking whether to Save All, Discard, or Cancel. This catches the common case of closing the laptop after a long debug session and losing the capture.

Probe does not auto-save — if you want a tab kept, save it explicitly.

Detail panel — what saved sessions render in
Search — runs across saved-session traffic too
Domain Watch — only captured (watched or teaser) traffic gets saved
Composer — replay any saved request with edits