Claron
    Documentation
    SESSION REPLAYS
    Live Debugging
    Reviewed

    Session Replays

    Inspect the activity and evidence captured during a review to understand the steps that led to an issue. Console and network details are available only when those capabilities were recorded.

    Capture a recording before the problem

    1. Start a review session on the intended environment and version

      In the extension, ensure Record Session Replays and the needed diagnostic capabilities are allowed for the device/project.

    2. Perform a short test action, then open Session replay in the review toolbar to confirm recorded activity is available.

    3. Reproduce the problem and submit the annotation

      End the session normally and allow the final save to finish rather than immediately closing the browser.

    4. Open Dashboard → Replays and locate the session by project/date/source, or open the report's replay window.

    Inspect the recorded activity

    Use the timeline to seek and change playback speed. Open the recorded clicks, console, and request panels to inspect the context at that point. Selecting a recorded click can seek to it; the DOM inspector examines the captured element rather than your current application DOM.

    Use the player's displayed shortcut help; controls depend on focus and the installed player version. Console/network entries only exist when those capabilities were captured.

    Portal, Console, and Guest describe recording sources, not a new permission grant. Filters help locate a source; they do not let a guest read staff-only diagnostics.

    Replay reconstructs recorded events. Cross-origin frames, unavailable assets, canvas content, sampled activity, and changed application state can limit fidelity. It does not guarantee perfect visuals or re-run the original server requests.

    Export and open a local replay

    1. Open the replay player and choose Download replay

      Save the exported recording file and keep it private.

    2. To inspect a supported exported .json or .json.gz recording, open Replays → Upload Replay and select that file

      Compressed recordings require browser support for gzip decompression. The local player reads it in your browser without creating a new cloud recording.

    3. Confirm that the imported file belongs to the session/version you intend to inspect

      An arbitrary JSON file or incompatible export is not a valid replay.

    4. Exporting or importing does not delete the original cloud recording or reduce its storage usage

      Manage retained data separately.

    Privacy, access, and availability

    Recordings and diagnostics can contain application text and data. Review with dedicated test accounts and avoid sensitive values. Input protection does not guarantee that the same data is absent from a page, console message, or request body.

    Project diagnostic permissions control cloud evidence access; a downloaded file is a separate copy that can be opened outside those permissions. Share exports only with authorized recipients.

    Active review sessions expire after 24 hours of inactivity. Cleanup of expired sessions can remove their replay data after the cleanup grace period; a replay is not a permanent archive. Export any recording you must retain while it is still available.

    For unavailable playback, check the project and filters, capture permission, session save state, access, and expiry. Legacy records may not distinguish never-recorded from expired. Start a new capture if the old activity was never recorded.

    KEY CAPABILITIES

    Replay reconstructs recorded interaction. It does not guarantee pixel-perfect playback or restore every external application state.

    Replay Data Points Captured

    Interaction Capture
    Records mouse tracking coordinates, clicks, scrolls, keystrokes, and hover coordinates dynamically.
    DOM Mutations
    Reconstructs captured DOM and style changes. Unavailable assets, cross-origin content, and unrecorded activity can limit visual fidelity.
    Console & Network Logs
    Shows recorded console messages and request details alongside playback when those capture capabilities were enabled.
    Rage Click Bursts
    Flags three or more nearby clicks on the same target, with at most one second and 30 pixels between consecutive clicks. Flame markers and activity entries jump to the recorded burst for review.
    Offline Playback
    Lets permitted users download an available recording for local playback. Exporting does not delete the cloud copy or reduce its storage usage.

    REVIEWING RAGE CLICKS

    Open a recording and select a flame marker to jump to a burst, or use the Activity tab to see its click count and timing. Selecting a problem shortcut or the rage-click summary starts 1.5 seconds before the burst so you can review the lead-up. Each rapid sequence counts as one burst. These signals suggest possible frustration; confirm the behavior in the replay and any available diagnostics.

    Text editing, common repeat controls, and Claron interactions are excluded. Add data-claron-no-rageclick to an element or its container to exclude an intentional repeated interaction. Detection runs when a recording is opened; project-wide rage-click totals and filters are not available. Older recordings may lack the metadata used to exclude automated or annotation clicks.

    REPLAYS DASHBOARD & SEARCH

    Navigate to Platform → Replays in the sidebar. The dashboard lists stored session replays available to your account and project access.

    Dashboard Filtering Controls

    Project Filter
    Limit the list to a single project to investigate project-specific UX issues.
    Session Mode
    Toggle between Solo review sessions and collaborative multiplayer sessions.
    Session Type
    Filter by Portal (hosted previews), Console (extension-based reviews), or Guest sessions.
    Time Range
    Query sessions started in the last 24 hours, 7 days, or 30 days.

    PLAYING BACK A SESSION

    Click the Play button beside any session. The player modal opens with:

    • Timeline scrubber: Drag or click to skip to specific timestamps. Highlights clicks and annotations.
    • Playback rate: Slow down to inspect race conditions or speed up through idle periods.
    • Metadata pane: Inspect viewport sizes, user agents, and total annotations created during the session.

    OFFLINE LOCAL REPLAY PLAYBACK

    To keep a local copy or inspect an authorized shared recording, export the replay and open the supported file locally. Export/import does not remove the original stored recording.

    Upload Local Replay File

    On the Replays dashboard, click Upload Replay and select a supported exported `.json` or `.json.gz` recording. Compressed files need browser support for gzip decompression. The Claron player loads the recording locally without uploading it to the cloud.