Skip to content

Session Manager

A session is a named, bounded capture — a start time, an end time (once stopped), a request count, and its own on-disk storage for bodies. Open it with ⌘2 or the toolbar icon.

Why sessions

Instead of one endless firehose of traffic, sessions let you:

  • Name a capture (“Checkout Flow”, “Onboarding QA”) so you can find it later
  • Attach filter rules to a session so only matching traffic gets recorded into it
  • Switch between sessions without losing earlier captures
  • Track disk usage per session and delete old ones to reclaim space

Working with sessions

  • Start: creates a new session, optionally with a name and filter rules attached.
  • Stop: ends the active session; it becomes read-only history.
  • Resume: reopens a previous session to keep adding to it (its live view state — scroll position, selection — is restored from a saved snapshot).
  • Rename / Delete: from the Sessions window toolbar.
  • Duplicate: clone a session’s transactions into a new one.
  • Export / Import: send a session out as TonyPack, HAR, or another supported format.

Disk usage

Each session tracks its own disk footprint (request/response bodies stored separately from the SQLite database). The Sessions window shows this per row, and deleting a session reclaims that space immediately.