01 / THE WORKFLOW
One continuous thread.
From found to fixed.
Ten moments. Keep the context captured along the way. Follow a bug from the tester’s first click to the fix your team can actually verify.
Tester finds a bug.
Just marks it.
Your app is hosted on Claron for testers to test. They run it, they find a bug. Instead of writing a messy, context-less ticket with maybe a screenshot at best — they just mark it. Right there on the page. Click the element. Done.
Review the
captured evidence.
Open an annotation to review the evidence captured for that report. Depending on permissions, report type, SDK instrumentation, and successful recording, it may include a screenshot, console or network details, element context, source attribution, or interaction path.
Claron It!
See The Bug, Live.
Reports with saved reproduction context can offer “Claron It!” button. It guides you through the captured steps toward the reported problem. The original account, assets, elements, or server state may not be recoverable, so confirm the behavior yourself. Try the live demo below.
Push reports
to your tracker.
Push a report to a configured issue tracker when your team is ready. Supported, enabled status sync can reflect changes in both directions. Comment and attachment sync depend on the provider and its configuration.
Review recorded
activity.
Replay the activity that was recorded. Pause at a captured point to inspect available DOM context, console logs, network requests, and page transitions. Coverage depends on recording permissions and successful capture; replay does not re-run the original requests.
Don't find the line.
We handle that.
Tired of hunting for the code you need to change? With matching source context, AI can suggest a code change for you to review. Apply it locally with the CLI or use a supported pull request workflow.
Terminal Cockpit.
Keyboard First.
Bring Claron directly into your command line. Inspecting annotations, triaging inbox issues, diffing code changes, and applying patches is a lightning-fast, keyboard-driven experience inside a beautiful local terminal cockpit.
Rebuild a configured
hosted preview.
A push can trigger a new build when the hosted preview integration is configured. Review before-and-after captures or pixel comparisons when that workflow provides them. Live production extension reviews do not support automated after screenshots or pixel comparisons.
Guide them.
Live.
Still not enough? Use Guided Mode and Spotlight to point things out directly on their screen. Same app. Same build. Same environment. Real-time collaboration on the actual running application.
Production bug?
We've got you.
Add the frontend SDK to supported JSX/TSX builds to attach source tokens to elements. Install it with npm install --save-dev @claron/sdk, then configure and verify the build integration. Source-map uploads are separate. Use the extension with approved capture permissions; live production reviews do not support automated after screenshots or pixel comparisons.