Free tool · no signup
Bug report generator.
Rant in, repro steps out.
Paste the Slack message, the support ticket or your own notes. The AI rewrites it as a report a developer can act on — title, environment, numbered steps to reproduce, expected vs actual, severity guess, suggested area — and tells you what is still missing instead of making it up.
Generate a bug report
The bug report template, explained
Seven fields. If a report has all of them, a developer can start on it without a follow-up question — that is the whole test.
- 01
Title
Where + what goes wrong. “Checkout: Pay now fails with 500 after a declined card”.
- 02
Environment
Browser + version, OS, app version or commit, account type, locale if relevant.
- 03
Steps to reproduce
Numbered, one action each, from a known starting point, with the data you used.
- 04
Expected
One or two sentences: what should have happened.
- 05
Actual
What happened instead — the observable behavior, not your theory.
- 06
Evidence
Exact error text, status codes, a screenshot or a recording. Timestamps if you have a video.
- 07
Severity
critical · high · medium · low — and say whether there is a workaround.
- auto
Or record it once
With a screen recording, SceneRecap fills every field from the pixels and the click log — steps from what you actually did, the first bad moment, console and network evidence, each linked to its second in the video.
How that works →
How to write a bug report
What makes a good bug report?
A title that names where and what breaks, the environment (browser, OS, app version), numbered steps to reproduce starting from a known state, what you expected, what actually happened, and evidence — the exact error text, a failed request, a screenshot or recording. A severity guess helps triage. That is exactly the structure this generator produces.
How do I write steps to reproduce?
One action per step, imperative voice, in order, starting from a state anyone can reach (“Open Reports from the sidebar”). Include the data you used (“filter: Last 30 days”). Stop at the step where the bug shows. If the generator cannot find a step in your text, it lists it under “Still needed” instead of inventing one.
Is there a bug report template I can copy?
Yes — generate a report and copy it as GitHub Markdown; the headings (Steps to reproduce, Expected, Actual, Environment, Evidence) are the template. Or paste this skeleton: Title · Environment · Steps to reproduce · Expected · Actual · Evidence · Severity.
Is the text I paste stored?
No. The description is sent to the AI model for this one request and is not logged or saved by SceneRecap. Don’t paste secrets anyway — redact tokens and passwords first.
Why is it free, and what are the limits?
It is a small taste of what SceneRecap does with a screen recording: there the AI reads the pixels, the clicks, the console and the network, and writes the report with every claim linked to its second in the video. The text tool is capped at 10 reports per day per visitor and the description at 4,000 characters.
Can it write the report from a recording instead?
Yes — that is the product. Drop a screen recording on the home page (no account) or install the Chrome extension; Bug Report mode returns numbered repro steps from your real clicks, the first bad moment, console and network evidence, and files to GitHub, Linear or Jira in one click.
Have a recording instead?
Drop it here and the AI writes this from the pixels.
No account needed for the first try. Up to 3 minutes, deleted after 24 hours unless you keep it.