How to write better bug reports
From "cannot reproduce"
to "fixed" in one take.
The slowest part of most bugs is not the fix. It is the three days of "what browser?", "can you send a screenshot?", "works on my machine." Moonshot compresses that loop into a single link.
What the engineer
actually receives.
One link that carries everything a fix needs, so triage starts with facts instead of questions.
The repro on video
Auto-zoom follows your clicks, so the crucial misclick is impossible to miss. The steps are the video, not a paragraph someone has to picture.
A written ticket, drafted by AI
From your narration: steps to reproduce, expected versus actual, and a suggested severity. You talk, it types.
Verified environment details
OS and hardware from the Mac app, or browser build, viewport, locale, and page URL from the Chrome extension. Nobody has to ask what version you are on.
One-click filing
Push to Linear, GitHub, or Jira, or straight into a Slack channel, using your connected accounts.
Talk through it once.
File it in one click.
You reproduce the bug and narrate. Moonshot does the transcribing, the writing, and the formatting.
1Reproduce and narrate
Hit the bug-report shortcut and walk through the issue out loud. Auto-zoom follows every click.
2Moonshot writes the report
The take is transcribed and turned into steps, expected versus actual, and a suggested severity.
3Review and push
Adjust anything, then push to your tracker. The ticket links to the exact moment in the recording.
Why this beats screenshots
and templates.
A template asks the reporter to remember twelve fields. A recording captures all twelve without asking.
Twelve fields to remember, and three days of follow-up when one is missing.
Built for the engineer
who has to fix it.
Triage by skimming
Chapters and the transcript turn triage into a skim, not a screening. Jump to the moment that matters.
Reply on the exact frame
If the video shows a fix candidate, reply right on that frame. Follow-up questions point at a second, not a paragraph.
Verified, not guessed
When the report comes through the Chrome extension, the environment block is verified data, not the reporter's best guess.
Bug reports, answered.
Does it work in the browser too?
Yes. The Moonshot Chrome extension records the tab or screen and attaches verified browser and system context to every report.
Which trackers are supported?
Linear, GitHub, and Jira issues, plus Slack delivery. All one click from the review screen.
Do reporters need to write anything?
No. Narrate while reproducing, and the AI drafts the ticket from the transcript. Edit if you like, file when ready.
File your next bug in two minutes.
Free to start, and no account needed until you want to share. Record the repro once, and the ticket writes and files itself.