Repros SDK
The SDK is what makes Customer Sessions work: it's the code, installed in your own app, that a customer's one-time report link claims when they open it. Install it once, anywhere in your app — it does nothing at all until a real report link claims it.
You only need this for Customer Sessions. Internal QA testers can keep using the Chrome extension, the SDK, or both — nothing here is required for QA.
Option 1: npm package
For an app with its own build step. Add it once, near the root of your app.
npm install @repros/sdkimport { init } from "@repros/sdk";
init();Option 2: script tag
For an app with no build step of your own. Add this once, near the root of every page.
<script src="https://www.repros.dev/sdk/repros-sdk.global.js"></script>What it actually does
Nothing, almost all of the time. The SDK looks for a one-time claim token in the page's URL — the one a Repros-hosted link redirects your app to after an account manager generates it and a customer opens it. No token, no network call, no UI, nothing mounted. That's deliberate: it's safe to leave installed on every page, permanently.
When a real token is present, it asks the customer to confirm before anything is recorded, then shows a small toolbar they can use to add a note and send the report. Console errors, failed network requests and a screenshot are captured only after they say yes, and only until they send the report.
One thing to check: pages behind your own login
The claim link lands on a Repros-hosted page first, then redirects into your app with the token in the URL. If the page it redirects to sits behind your own login wall, your login flow's own redirect can strip that token before the SDK ever sees it.
Point report links at a page a customer can reach without signing in to your app, or make sure your login redirect preserves the original query string.