DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to capture and drive the Burp window for a bug report with Reburp

Take screenshots of Burp and switch tabs or click elements over REST to document a finding.

Authorization notice. Reburp is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA tester or extension developer writing a report or reproducing a UI-dependent Burp workflow who wants an agent to show each step.

The problemWriting up a Burp workflow with screenshots takes manual steps, and reproducing the same clicks for each report is tedious.

The outcomeA set of screenshots showing each step, taken and driven through the UI routes, ready to attach to a report.

What you need first

  • Burp Suite with the Montoya API (reburp 1.1.14 lists 2026.7 as minimum; older Burp needs the matching older jar from Releases)
  • The reburp-*.jar from the Releases page, or Java 17+ to build from source
  • Written authorization to test the target systems
  • A terminal with curl, or an AI agent that can make HTTP calls to 127.0.0.1:9090

Steps

  1. Load Reburp.jar in Burp and confirm the server with curl -s http://127.0.0.1:9090/api/status.
  2. Open http://127.0.0.1:9090/docs and find the UI group under /api/ui/ in the spec.
  3. Call the UI routes to list tabs, switch to the tab you need, and take a screenshot of the window or element. (inferred, check the README)
  4. Use the click, type, or select routes to reach the dialog or element that shows the issue, then take another screenshot. (inferred, check the README)
  5. Save the screenshots with the report and check that each one matches the step it documents.

Prompt for your agent

Using the reburp API at http://127.0.0.1:9090 with the spec at /openapi.json, switch Burp to the <tab name> tab, click <element label>, and take a screenshot of the Burp window at each step. Return the screenshot files with a one-line description of each, and verify each screenshot shows the tab or element named before reporting it.

Caveat. The UI routes act on the live Burp window, so run them only when you can watch the screen, because a click can change project state.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page