1Record steps
Open the extension and choose Record Steps before you repeat the issue.
Featured in the Chrome Web Store
Record the steps behind the bug.
When a bug disappears on a fresh page, the steps before it matter. Record your browser steps, replay what happened, and share the recording with engineering.
Trusted by 2,000+ professionals weekly across quality assurance, engineering, and support.
See the steps a screenshot leaves out.
Two selected tickets. A page change. A disabled button. Explore the steps that explain why the same page can look different to your teammate.
Assign button disabled after a page changeExample using test data
Step 4 of 5
Browser steps
The count still says two, but no rows are selected and the button is disabled.
button[data-testid="assign-selected"]An illustrated walkthrough using test data. Select a step to see how the page changes.
The bug happened before the screenshot.
A switched account. A selected row. A page change. Earlier actions can explain why you see a bug and your teammate doesn't.
- The reporter selects two tickets, then changes the page.
- The engineer opens the same page in a fresh tab.
- Same page, different starting point. The earlier steps are missing.
After the earlier steps
2 selectedAssign disabledThe count and the selected rows no longer agree.
The reported issueOn a fresh page
0 selectedAssign disabledNothing is selected. The button looks normal.
Earlier steps missingRecord it. Review it. Share it.
Start recording before you repeat the issue. Stop and review what was captured. Share the recording with the teammate investigating it.
2Stop & Save
Review what was captured. Save the recording to your workspace with a free account.
3Share recording
Share with project members, or create a public link. Check who can open it before sending.
Illustrated steps. Your recording stays under your control.
Explore the stepsExample using test data
The count still says two, but no rows are selected and the button is disabled.
Go straight to the step that needs a closer look.
Replay the recorded actions and inspect the affected button or field. Keep the available browser details beside the step you're investigating.
Try the previous and next steps in this example. The change from page one to page two explains the stale selection count.
Keep the details that help engineering investigate.
Review the recording, the affected element, and the browser details captured with it.
Recorded steps
The ordered actions leading to the failure.
Affected button or field
The element involved in the issue.
Page and browser details
The available page, browser, and viewport context.
Notes for your teammate
What you expected, and what happened instead.
Selectors for this example
CSS selector
button[data-testid="assign-selected"]Playwright locator
page.getByTestId('assign-selected')Exported test code is a starting point. An engineer reviews it and adds the setup, test data, and checks your application needs.
Put the recording where the bug is being discussed.
Add the recording link to the issue your team already uses. Your teammate can open it and review what happened.
See sharing and integrationsExample issueExample using test data
BUG-042 Needs investigation
Assign button disabled after a page change
I selected two tickets, then went to page two. The count still says two, but I can't assign them.
See the browser stepsExplore the example abovePrivate recordings need project access. Public links can be opened by anyone who has them.
Review what you share. Choose who can open it.
Input values are masked by default, but other page content can still appear. Check the recording before sharing it.
Before you record your first bug
Does it record all my browsing?
You start a bug recording when you want to capture a problem. The extension records the browser steps you choose to record.
Can I use it without writing code?
Yes. You can record browser steps without writing code. Your teammate can review the recording and inspect the available technical details.
Do I need an account?
You can try the extension before signing up. Create a free account to save and share recordings through your workspace.
Will it fix the bug or create a finished test?
You still investigate and fix the issue. If you export test code, review it and add the setup, test data, and checks your application needs.
Can it show what happened before I started recording?
No. Start recording before you repeat the steps that lead to the issue.
What does the free plan include?
You can start with short recordings and try sharing an issue with your team. See the current recording length, sharing, and account limits on the pricing page.
Who can open a recording I share?
Private recordings require access to the project. If you make a recording public, anyone with its link can open it. You can make it private again to remove public-link access.
Give engineering the steps to investigate.
Start with a short browser recording and review it before you share.