Debug the behavior. Start with the recording.
A bug report is a better starting point when you can follow the clicks. Replay the browser steps, inspect the affected element, and bring that context into your investigation.
Free extension for desktop Chrome. Try it before signing up.
- Element
- button
- Text
- Calculate renewal
- data-testid
- calculate-renewal
The action is recorded. The underlying cause is yours to investigate.
Switch between the element details and the actions that led here.
- YOUR QUESTION
- What led to this state?
- KEEP THE CONTEXT
- Recorded actions + element details
- GIVE YOUR TEAM
- An investigation grounded in the browser
Less reconstructing. More to work with.
The final screen tells you something went wrong. The steps and the affected element give you somewhere specific to look.
Try the interactive recording- 01
Replay the path that reached the bug.
Move through the recorded actions and page changes. Find the moment the observed behavior diverged from what the reporter expected.
- 02
Inspect the element in that moment.
Review its available attributes, selector candidates, and captured context. Keep a note attached to the element you want to investigate.
- 03
Continue in your development workflow.
Retrieve authorized recording evidence through MCP or review a generated Playwright draft. Add your setup and assertions, then run it in your environment.
Useful for your next investigation.
A few useful answers.
Know what you can capture and how to share it.
Recording privacy & accessDoes this replace my debugger or error monitoring?
No. Samelogic preserves a deliberately recorded browser workflow and inspectable element context. Use your debugger, error monitoring, and application logs to investigate the underlying code and services.
Can an AI assistant investigate the recording?
Supported MCP connections let an authorized assistant retrieve recording and element evidence. The engineer still reviews the diagnosis, proposed code changes, and verification results.
Is a generated Playwright draft a finished test?
No. Review the draft, provide application setup and fixtures, add meaningful assertions, and run it. A captured interaction is evidence of a browser action, not proof that a test passes.
Your next investigation. A clearer starting point.
Record the steps. Review what happened. Give your teammate the context to begin.