For QA, support and engineering
Screen recording in.
Bug report out.
Reproduce the bug once in Chrome. SceneRecap watches the pixels, the clicks, the console and the network, then writes the bug report — repro steps, expected vs actual, first bad moment, evidence — every line linked to its second in the video. File it to GitHub, Linear or Jira in one click.
How it works
- 01
Record the bug
Click the SceneRecap icon, pick Bug Report mode, reproduce the problem. No need to talk — but you can.
- 02
The AI watches
Sampled frames, every click and navigation, console errors, failed requests, page titles — all timestamped while you record.
- 03
Get the report
Repro steps, expected vs actual, first bad moment, evidence, severity, and a paste-ready issue body. Share the link or file the issue.
What is in the report
See a real one: Checkout payment failure (402 → 500) — generated from a 70-second silent recording.
Numbered repro steps
Written from what you actually did — with the timestamp of each step as a seek link.
Expected vs actual
Two short paragraphs a developer can act on, not a wall of text.
First bad moment
The second things went wrong, marked on the timeline and in the report.
Console & network evidence
Uncaught errors, failed requests (status + duration), and visual evidence — captured automatically, cited with timestamps.
One-click filing
Create the issue in GitHub, Linear or Jira with the AI-written body. Slack gets a ping if you want.
Reviewer-safe by default
Passwords and payment fields masked at capture; keystrokes never logged; you review before upload.
Frequently asked
Does it really write the bug report for me?
Yes. Bug Report mode is the one thing the AI is told to be exhaustive about: it reconstructs the steps from your clicks and navigations, names the first bad moment, and attaches every console error and failed request it saw, each with a timestamp. You edit, then file.
Do I have to narrate the recording?
No. SceneRecap reads the screen and the interaction log, so a silent recording produces a full report. If you speak, the transcript is used as extra context.
Which issue trackers are supported?
GitHub, Linear and Jira with one-click filing; Slack for notifications. You can also copy the report as Markdown for anything else.
Is this like Jam?
Jam captures bug context (console, network, screenshot or clip). SceneRecap records the whole session and has the AI write the report from it — and the same recording can also become a tutorial or a recap. See the comparison page.
What does it cost?
Bug Report mode is included in the Free plan (25 recordings, up to 10 minutes each). Pro removes limits and adds PDF/DOCX exports, integrations, API and voiceover.
Stop writing bug reports by hand.
Record it. SceneRecap writes it.
Free plan · No card · EU hosted