Visual bug reports, session replay, and AI-assisted fixes — connected for testers and developers.

One connected workflow

1. Mark it: Point at the problem.

   Testers mark a problem on your preview. Depending on capture permissions and report type, Claron can include a screenshot, logs, network details, and DOM context.

   Screenshot · Console · Network · DOM

2. Replay it: See how it happened.

   Review the recorded session. Inspect available DOM, console, and network context from captured activity.

   Session replay · Synced events

3. Fix it: Take context into code.

   Jump from the report to source context. Let AI propose a fix, then apply it locally or open a pull request.

   Source mapping · AI fixes · Pull requests

Your app. Our common ground.

Claron is a shared workspace for testers, clients and developers, built around your running website or app.

Work on the same version, in the same environment. With everyone looking at the same thing.

Bugs wash up. Claron catches them.

Five things that happen at the water’s edge, from the first report to the bug you never saw coming.

1. Visual bug reporting: Spot a bug.
   Just mark it.

   Testers click the element, right there on the running page. Claron pins the report in place with its context attached: no screenshots pasted into chat, no vague descriptions.

2. Claron It!: Walk straight back
   to the bug.

   Reports with saved reproduction context offer a “Claron It!” button. It guides you through the captured steps toward the reported problem, so you can see it live and confirm the behavior yourself.

3. Live collaboration: Guide them.
   Live.

   Use Guided Mode and Spotlight to point things out directly on their screen. Same app, same build, same environment, with everyone’s cursor in the room. Clients can join as guests, without a Claron account.

4. Ticket sync: Push it to
   your tracker.

   Send a report to Linear, Jira, Trello and more when your team is ready. Supported, enabled status sync can reflect changes in both directions.

5. Production reporting: Production bug?
   We’ve got you.

   Report right on your live site with the Claron browser extension, using approved capture permissions. Add the Claron SDK to your build, whichever frontend framework you use, and every production report points straight back to the source element.

1. Session replay: Rewind the bug.
   Watch it happen.

   Every report carries the session that led to it. Scrub through the visit with the page, console and network in sync, and see exactly what your tester saw, step by step.

2. Backend evidence: Follow the request.
   Into your server.

   Claron matches each request in the session to what your server did with that exact request: the functions it called, the branches it took, the error it threw. Your own collector encrypts it; it is decrypted only on your device.

3. AI Fix: Find the cause.
   Ship the fix.

   Claron follows the bug from the page to the line of source that caused it, explains why, and writes the change. Apply it in your CLI, or raise the pull request from here.

4. Claron CLI: Your clone.
   Still out of date.The same fix.
   On your machine.

   The fix is upstream. Claron CLI brings the verified patch into the clone on your own machine.

5. MCP: Your own agent.
   Reads the bug.

   Claron's MCP server hands your coding agent the whole investigation: the issue, console, network, session, screenshots and backend references. Read-only, and limited to what your role can see.

6. Auto-rebuild: Push the fix.
   Claron rebuilds.

   Push to your project's branch and Claron rebuilds its review build by itself, then tells whoever reported the bug that the fix is live to check.