“I can reproduce this bug.”
Record the steps, inspect the affected element, and give engineering a specific reproduction to investigate.
Samelogic helps you record and inspect a bug you can reproduce. Sentry Session Replay connects captured user sessions to production errors, logs, and traces.
Free extension for desktop Chrome. Try it before signing up.
Record the steps, inspect the affected element, and give engineering a specific reproduction to investigate.
Connect a captured session to its errors and traces. Follow what the user did alongside the diagnostics your application collected.
Explore Sentry’s approachBoth tools let you replay activity and inspect elements. The difference starts with how you capture the issue and the context you need beside it.
| YOUR WORKFLOW | Deliberate browser recording | |
|---|---|---|
| Getting started | Install an extension. Start a recording. Capture an issue in desktop Chrome without adding an SDK to the application. Try local recording and replay before signing up. | Enable Replay in your application. Add the Replay integration to Sentry’s browser SDK. Configure which sessions to sample and when to capture around errors. Documentation |
| Recording & diagnostics | Follow a reproduction you recorded. Capture the steps you take and the page changes they produce. Recording starts with you; earlier browsing cannot be recovered. | Connect a session to production diagnostics. Follow captured user activity alongside errors, traces, console output, and network requests. Coverage depends on SDK setup and sampling. Documentation |
| Element inspection | Keep the affected element with the report. Pause the replay, select an element, and review its selectors, attributes, and styles. Attach a note to that moment. | Inspect the recorded DOM. Select an element in a web replay to inspect its HTML structure, attributes, and position in the document tree. Documentation |
| Engineering handoff | Share the reproduction and its context. Link a recording, create a Jira Cloud or Linear issue, or export a Playwright test draft for an engineer to review and run. | Share the relevant moment in a session. Send a replay at a specific timestamp to another Sentry member in your organization, with the available debugging context alongside it. Documentation |
| AI & coding agents | Give an agent the recorded evidence. Read-only MCP tools expose authorized recordings and element context. Review and verify any fix or test the agent proposes. | Investigate with Sentry’s wider platform. Sentry MCP connects coding tools to error and performance data. Seer adds AI investigation and proposed fixes; it is a separate add-on. Sentry MCP Seer AI debugging |
| Privacy & capture | Review what you recorded. Input values are masked by default. Other page content can appear, so review the recording and its access before sharing. | Configure what Replay can capture. Text and input values are masked and media is blocked by default. Adjust masking and blocking rules for your application. Documentation |
Written by Samelogic. Vendor documentation checked September 27, 2026. Availability depends on configuration and plan.
Three seats on screen. Two in the quote. A recording preserves the extra click and the affected button, so the next engineer can follow what happened.
The extra seat never reached the quote.
“I added a third seat, but the quote still uses two.”
A Sentry issue can point you to the failure. When you can reproduce it, record the sequence with Samelogic and bring both views into the investigation.
A manual handoff. Set access for each link. Native Sentry linking and automatic error matching are not yet available.
Try local recording for free. Check workspace limits for saving, sharing, and team use.
Samelogic plansCheck the replay quota, additional usage, and retention in your plan. Seer is a separate add-on.
Sentry pricingUse Samelogic to record an issue you can reproduce and pass its steps and element context to engineering. Use Sentry to investigate captured production sessions with errors, traces, and other diagnostics. Samelogic does not replace production observability. The two workflows can complement each other.
No. Install the extension in desktop Chrome and record on a supported page. Local recording and replay are available before signup. Saving and sharing through a workspace needs an account, and plan limits apply. Sentry Session Replay needs its browser SDK and Replay integration configured in the application.
Samelogic cannot recover activity from before you started a recording. With Sentry’s SDK already running and error-based sampling configured, Replay can keep a buffer of up to one minute before a sampled error. What is available depends on your capture settings and when the SDK initialized.
Yes. Its web replay supports DOM inspection, including HTML and attributes. Sentry also offers MCP access to its platform and Seer for AI investigation and proposed fixes. Those broader platform features have their own setup and availability; Seer is a separate add-on.
You can manually add the Samelogic recording link and the Sentry issue or replay link to the same engineering ticket. Check access to each link for your teammate. A native Samelogic–Sentry connection and automatic error matching are not currently available.
Samelogic can export recorded actions as a Playwright test draft. An engineer still needs to review the setup, locators, and assertions, then run the test. Neither a recording nor an exported draft proves that the bug is fixed.
This comparison is written by Samelogic, using current product capabilities and the Sentry documentation below. It is a workflow guide, not a hands-on performance benchmark. The logos identify each product and do not imply an affiliation.
Record the steps. Inspect the affected element. Give your teammate a reproduction they can follow.
Add to ChromeFree extension for desktop Chrome.