Can we rebuild it?
Culprit icon

Can we rebuild Culprit?

Build a Chrome extension like Culprit — a Culprit alternative you own.

You can build your own Culprit Chrome extension in a single sitting using native web APIs. Instead of relying on closed-source software to observe your web sessions, a custom alternative lets you intercept fetch and XHR requests, attach user click trails, and format actionable bug reports tailored directly to your team's debugging workflow.

Users
60
Rating
★ 0
Category
—
Verdict
YES

The listing record

NameCulprit
Store rating0 / 5
Users60
Store listingChrome Web Store ↗
Analyzed7 November 2026

What Culprit does

Every failure leaves a clue. Capture API failures, find reliable test selectors, and create actionable bug reports, all in one free, privacy-first Chrome extension. It is free to use; it is proprietary software and its source code is private. A page breaks and the bug report says "it doesn't work". Culprit shows what really happened: you did this this broke copy it. Switch it on for a site and it watches that site's API calls (fetch and XHR), console errors, uncaught errors and broken resources, then ties each problem to the click that set it off. For example: "Clicked Submit order POST /api/orders returned 500 two tenths of a second later".

What the store says

★ 0 · 60 users

Pulled live from the Chrome Web Store listing at analysis time.

Can PlugThis rebuild Culprit?

YESYes — you can rebuild this.

“It's just an injected listener wrapping fetch, XHR, and clicks into a timeline.”

Culprit relies entirely on standard browser APIs: wrapping window.fetch and XMLHttpRequest, capturing window.onerror, and listening to click events. A content script running in the main world context can correlate user clicks with subsequent failed network requests and console errors entirely on the client side.

What's actually hard to replicate
DOM event correlation logicMain-world script injectionSelector generation heuristics

Why build your own Culprit alternative

  • Full control over where sensitive bug reports and API payloads go
  • Custom formatting for your team's issue tracker like Jira or GitHub
  • Ability to filter out noise from known third-party tracking scripts
  • Zero risk of proprietary telemetry collecting your internal network calls

What it costs vs what you'd save

The original: Free

Your version: While the original is free, building your own ensures internal network payloads and proprietary site interactions never leave your browser or hit closed-source software.

The starter prompt

Starter prompt — paste into PlugThis
Build an extension that logs user interactions and correlates them with network and console errors. Inject a script into the page that wraps fetch and XMLHttpRequest to detect non-2xx status codes, listens for uncaught errors, and captures click events with unique element selectors. When an error occurs, correlate it with the preceding click and provide a popup or side panel to copy a clean, markdown-formatted bug report.
Build it with PlugThis →

Features you could add that Culprit doesn't have

Because you own the code, these are a follow-up prompt away — tap one to add it to the prompt above.

  • GitHub Issues Exporter — Directly convert correlated failure logs into formatted GitHub issues with one click.
  • Payload Redactor — Automatically scrub sensitive tokens, passwords, and PII from request payloads before generating the report.
  • Console Log Streamer — Include recent `console.warn` and `console.error` traces alongside the network failure.

Questions about rebuilding Culprit

How does the extension intercept fetch and XHR requests?

It injects a lightweight script into the page's execution context to wrap `window.fetch` and `XMLHttpRequest.prototype.open`, recording request URLs, methods, status codes, and timings.

Can it link a failure to the user's specific click?

Yes. A global click listener records the target element and its CSS selector with a timestamp, correlating any failed API call or uncaught error occurring shortly after that action.

Does this require a backend server?

No. The tracking, selector generation, and report assembly run entirely client-side, copying bug reports straight to your clipboard or pushing to GitHub via its REST API.

How to build it yourself

  1. 1
    Open PlugThis and start a new build

    Head to PlugThis and start a new Chrome extension. You're describing a Culprit alternative you'll own outright — no store subscription.

  2. 2
    Paste the starter prompt

    Paste the starter prompt above. PlugThis expands it into a full Manifest V3 extension — popup, content scripts, and service worker included.

  3. 3
    Review, tweak, and load it

    Review the generated code, ask for tweaks in plain English, then download and load the unpacked extension in Chrome to try it.

  4. 4
    Publish it (optional)

    When you're happy, publish your Culprit alternative to the Chrome Web Store — or just keep it as a private tool for yourself.

Build your own Culprit alternative

Describe it in plain English. PlugThis generates the full Manifest V3 Chrome extension in about two minutes.

Build it with PlugThis →

More teardowns

We run the same teardown on any Chrome extension — what it does, whether a self-built alternative holds up, and the prompt to make one. Tear down another extension, or see the extensions we've actually rebuilt and filmed — real build times, real prompts, real recordings.

Sources & verification

  • All facts pulled live from the Chrome Web Store listing ↗.
  • The verdict is drafted by the PlugThis teardown engine — an opinion about buildability, not affiliation with Culprit.
  • Written by PlugThis, which builds Chrome extensions from plain-English prompts.

Published and last updated 7 November 2026. Figures reflect the Chrome Web Store listing on that date and may have changed since.