Browser support
Which browsers BugCapture runs on, and what a strict CSP can block.
Supported browsers
| Browser | Support |
|---|---|
| Chrome | Full support |
| Edge | Full support — runs the Chrome package unmodified |
| Brave, and other Chromium browsers | Generally works; not individually tested the way Chrome and Edge are |
| Firefox | Full support, from a separate package |
Chrome and Edge are the primary targets and get the widest testing. Firefox support requires Firefox 140.0 or later.
What it can capture
Any web page you can open, including staging environments, internal tools, and localhost. The extension does the capturing — the page you're on doesn't need to install anything or add a script.
What it can't reach
- Browser-internal pages —
chrome://,about:,edge://and equivalents. Browsers don't allow extensions to run there. - Other extensions, and the extension stores themselves — same restriction.
- A page with an unusually strict Content Security Policy may block part of the console capture. The screenshot, environment info, and everything else still works — only the console log is affected, and only on pages that go out of their way to restrict it.
Recording
Screen recording captures a tab or a region of it — never your whole desktop. That's deliberate, not a current limitation: nothing else open on your machine can end up in a bug report by accident.
Mobile
There's no BugCapture browser extension for mobile browsers. For bugs inside a native app, see the React Native SDK and the mobile companion app — both file into the same reports your team already triages.