Captain Octopus — Local-First Bug Capture

Octopus turns "cannot reproduce" into a replay. Record a bug once and hand your engineers everything they need to fix it — a replayable session, the console, the network, and the exact steps that led to the failure. Everything is captured and redacted on your own device. There is no account, no server, and nothing is ever uploaded. WHY OCTOPUS A tester swears a button breaks. The developer clicks it and it works. A screenshot misses the console error, the failing request, and the three steps that actually triggered the problem — so the ticket bounces back and forth for days. Octopus captures the whole story the moment it happens, so the bug is reproducible instead of debatable. HOW IT WORKS Start recording. Click the Octopus toolbar icon and press Start. A small pill appears in the corner of the page to show the tab is recording. Capture is off until you ask for it — nothing is buffered while you are not recording. Reproduce the bug. Do the thing that breaks. Octopus records a replayable session of the page along with the console, network activity, and every click, input and navigation. Stop and get the report. Press Stop (from the popup or the on-page pill) and Octopus builds a report and opens it in a new tab: a scrubbable replay lined up with the console, network and reproduction steps, ready to attach to a ticket. WHAT IT CAPTURES A replayable DOM session — the page is recorded as it changed, so the report plays back like a video you can scrub through. Because it is real markup rather than a movie, text stays crisp and searchable. Console — every log, warning and error, plus uncaught exceptions and unhandled promise rejections, with their arguments and stack traces. Network — fetch and XHR requests with method, URL, status, timing, and size-capped request and response headers and bodies. Reproduction steps — your clicks, inputs and navigations become a clean, numbered "how to reproduce" list, aligned to the replay timeline. Screenshots — a viewport screenshot is captured for the key steps so the report has visual context. PRIVACY-FIRST, BY DESIGN Octopus is local-first. Recording, redaction, storage and the report viewer all run on your machine. No account, no sign-in, no analytics, no server. A redaction pass runs locally BEFORE anything is stored: authorization and cookie headers, tokens and API keys, emails, credit-card and SSN patterns, and password fields are masked by default. You can add your own CSS selectors and regular-expression patterns to mask more. Reports are stored in your browser and open in an in-extension viewer — there is no cloud dashboard and no shareable server link. A report only leaves your device if you explicitly export it as a portable .zip, which you or a teammate can re-import into Octopus. WHO IT IS FOR QA engineers and testers who want to file a bug developers can actually reproduce. Developers who would rather open a replay and read the failing request than guess from a screenshot. Product managers and support teams who need to capture an issue faithfully without knowing their way around DevTools. Privacy-conscious teams who want rich bug reports without shipping session data to a third-party cloud. Octopus is part of the Pirates of Bugs toolkit.