From 0a477fd288d064d265395c88dbd0f261b723804e Mon Sep 17 00:00:00 2001 From: spiperac Date: Mon, 15 Jun 2026 06:42:13 +0200 Subject: Initial release --- docs/features/loot.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 docs/features/loot.md (limited to 'docs/features/loot.md') diff --git a/docs/features/loot.md b/docs/features/loot.md new file mode 100644 index 0000000..5c82e88 --- /dev/null +++ b/docs/features/loot.md @@ -0,0 +1,24 @@ +# Loot + +The Loot tab is a findings tracker. When you find something worth documenting during a test, you save it here with the relevant request and response attached. + +## Adding an entry + +Click **Add** to open the entry dialog. Fill in: + +- **Title** — a short name for the finding +- **URL** — the affected endpoint +- **Severity** — Critical, High, Medium, Low, or Info +- **Notes** — a free-text field for your write-up, reproducing steps, or anything else. Supports Markdown. + +You can also send a request directly from the History or Repeater tab using the Loot button. This pre-fills the raw request and response fields so the evidence is captured automatically. + +## Managing entries + +Entries are listed in a table with title, URL, and severity. Clicking a row expands the detail view showing notes and the raw request/response. + +Right-clicking an entry gives options to edit it or delete it. + +## Export + +The **Export** button writes all loot entries to a Markdown file. The output includes each finding's title, severity, URL, notes, and the raw request and response in fenced code blocks. The format is clean enough to paste directly into a report or a Git repository. -- cgit v1.2.3