Record the bug
Give your agent the steps to reproduce, or record them yourself in Chrome. Show what happened and explain what you expected.
Record the bug, create a ticket with the video, and send it to Slack. Your team gets the steps, the evidence, and a place to follow up.
Connects your library and sessions. To record a browser, add the local recorder.
Recording and seats are free. AI processing uses credits. All features are included on every plan.
Record the bug in the checkout flow. Show the steps that trigger it and note what should have happened. Return the video link for the ticket.
Give your agent the steps to reproduce, or record them yourself in Chrome. Show what happened and explain what you expected.
Use a connected issue tracker to create a ticket from the recording. Review its title, summary, and reproduction steps.
Post the ticket and recording links to your team’s Slack channel. The next engineer can watch the issue before picking it up.
The sequence matters: where you clicked, what loaded, and when the result changed. Recording the flow preserves details that are easy to miss in a written report.
Ask your agent to reproduce the issue in its recording browser, or use the Chrome extension to capture it yourself. The uploaded recording gets a share link, with transcript and summary processing available from your workspace credits.
Create a Linear, GitHub, or Notion ticket after connecting the relevant integration. Review the ticket, then share it and the recording in Slack. Engineering gets the expected result, reproduction details, and the video in one handoff.
Share the exact interaction sequence alongside the reproduction steps.
Show engineering the behavior you can reproduce, without rebuilding the explanation in chat.
Use hosted MCP search to find related recordings and read their transcripts during triage.
Capture the issue, attach the evidence, and bring the team into the loop.
Connects your library and sessions. To record a browser, add the local recorder.