Organizer

The Organizer is a triage workspace for interesting requests you want to revisit. Save flows here with notes, tags, and categories — keep your “stuff to look at later” pile separated from the firehose of the main HTTP History.

Think of it as a curated bookmark folder for flows. Findings are for confirmed vulnerabilities; the Organizer is for hunches and works-in-progress.

🔗Saving Requests

From any flow in the Logger or Search view:

  • Right-click → Save to Organizer
  • Or multi-select → Bulk Save to Organizer

Each saved entry captures:

  • Snapshot of the flow at save time (request + response + headers)
  • A free-form note field
  • A category (your taxonomy — see below)
  • Tags (multi-value)
  • Priority (Low / Medium / High / Critical)
  • Created/updated timestamps

The flow itself stays in History; the Organizer entry is a separate record that points to it.

🔗Categories

Build your own categorisation to fit how you triage. Common starter categories:

  • recon — endpoints worth deeper inspection
  • auth-flows — login / logout / refresh flows
  • idor-candidates — params worth privilege-escalation testing
  • admin-paths — anything that smells like admin functionality
  • js-of-interest — JavaScript files with sinks worth analysing
  • weird — responses that surprised you and need explaining
  • repro-needed — bugs you saw once and need to reproduce

Categories are project-scoped. Create them inline as you save flows.

🔗Search & Filter

The Organizer table supports:

  • Full-text search across notes, tags, URL, body
  • Filter by category, tag, priority
  • Filter by status (Open / In-Progress / Done / Discarded)
  • Sort by saved-date, priority, last-updated

🔗Status Workflow

Each entry has a status to track triage progress:

Open → In-Progress → Done
                 ↘ Discarded
  • Open — newly saved, not yet looked at
  • In-Progress — actively investigating
  • Done — confirmed (usually means a finding was created)
  • Discarded — false alarm, no impact

Status updates with one click; bulk update via multi-select.

🔗Bulk Actions

  • Bulk tag / untag
  • Bulk change category
  • Bulk set priority
  • Bulk mark status
  • Bulk delete
  • Bulk export

🔗Promote to Finding

Each entry has a Promote to Finding button — opens the New Finding dialog pre-populated from the saved snapshot (URL, method, evidence body, etc.). The Organizer entry is auto-marked Done with a link to the new finding.

🔗Triage Workflow

  1. While testing, save flows that look interesting (don’t stop to investigate — keep flow)
  2. End of session, open Organizer
  3. Sort by Priority desc, status=Open
  4. Walk the list: investigate, then mark In-Progress / Discarded / Promote to Finding

🔗Export

Export the entire Organizer as JSON for sharing with collaborators or for offline review:

  • Full snapshots
  • All metadata
  • Status history

🔗MCP

The organizer MCP tool exposes:

  • list — all entries with filters (category / tag / status / priority)
  • get — one entry by id
  • save — save a flow with note + category + tags
  • update — change note / category / tags / status / priority
  • delete
  • search — full-text search
  • categories — list all categories used in the project
  • tags — list all tags
  • bulk_tag — apply tag to multiple entries
  • bulk_delete
  • export

LLM agents can use this as scratch space — “I’m exploring this API, save anything interesting to organizer with tag agent-discovered so the human can review later”.