Browser Extension
The Claron browser extension lets you report issues on an existing website, using the pages and signed-in state available to your browser. Keep the website on its current host and authorize the project before capturing.
Before you start
A supported Chromium browser and an approved device, project, and website origin.
What you get
Reports captured on your existing website, with the evidence you chose to enable.
Choose extension capture permissions
INTERACTIVE EXAMPLETry an approved project's capture choices before starting a review.
Storefront · staging.example.com
Approved example deviceAllow only the capture needed for this review.
Install and authorize the extension
Install Claron Live Review from the Chrome Web Store listing linked below
Open the extension in a supported Chromium browser.
Sign in or follow the extension's device activation flow
If activation uses an API key, the key needs extension:create; an MCP read-only key does not grant this permission.
Open Claron Settings → Developer & API and approve the intended extension device and project access
Check the approved website origins before continuing.
Enable only the permitted capture capabilities you need: annotations, screenshots, DOM context, console, network metadata, interaction breadcrumbs, replay, or collaboration.
Open the approved website, refresh the tab after activation if requested, and select the correct project and environment in the extension.
Start a review and submit a report
Start the review from the extension on the approved website
Log into your website normally if it requires authentication.
Choose Point or Element, select the problem, and write the expected result and reproduction steps
Inspect permitted console or network evidence when that context is relevant.
Submit the annotation
Open it in Claron and check its URL, environment, screenshot state, and the diagnostic evidence you expected.
For file/line attribution on JSX/TSX elements, add the frontend SDK and make a new deployment first
For your server's request context, enable backend evidence before a new review.
Capture choices and website access
The extension uses the access your browser already has. It does not grant permission to bypass a login, corporate firewall, or site access control. Use approved accounts and domains.
Replay and diagnostic capture are separate permissions. Realtime message text needs an additional explicit per-session opt-in; metadata alone does not imply message content was recorded. Avoid entering sensitive test data and review evidence before sharing a report.
A production report preserves the available report-time capture. Automated screenshot retakes, after screenshots, and pixel comparisons are unavailable for live production annotations. Use human verification on the target deployment instead.
When capture does not start
Check that the browser supports the extension, the device is approved, the project grant includes the current origin, the key has extension:create if used, and the requested capability is enabled. Refresh the tab after changing a grant.
A disabled capture capability cannot be recovered retroactively from an old report. Enable it and create a new review. For source-resolution failures, check the matching deployed SDK build.
Remove or revoke the device/project grant from Developer & API when that device should no longer capture. Signing out or uninstalling locally is not a substitute for revoking a still-active credential.