Capture the repro on screen and Moonshot writes the report: steps to reproduce, severity, and your environment details, ready to push to Linear or GitHub in one click.
Three steps, all from one recording. You trigger the bug once, and the ticket arrives with evidence attached.
Trigger the bug on screen and narrate what you expected. That narration becomes the report.
Steps to reproduce, expected vs actual, severity. Moonshot drafts it from the recording, with your OS, build, and hardware attached.
Linear or GitHub. The ticket carries the video, so engineers watch the failure instead of imagining it.
"Cannot reproduce" usually means "the report skipped a step". Video skips nothing.
The steps come from what you actually did on screen, in order. No reconstruction from memory an hour later.
recording → steps 1-2-3macOS version, build number, hardware. Moonshot collects it at capture time and threads it into the report.
zero "what version?" pingsPush the finished report to Linear or GitHub with the recording linked. Triage starts with evidence.
report → MOON-481A written report with steps to reproduce, expected and actual behavior, severity, environment details, and a link to the recording with captions and transcript.
Capture runs on macOS with Apple silicon. Tickets, share links, and the web library open anywhere, so a mixed team can watch and triage from any OS.
Close. Moonshot exposes recordings over MCP, so an engineer can point Claude or Cursor at the library, pull the transcript, and even draft a fix from what the recording shows.
Free to start, and no account needed until you want to share. Record the repro once, and triage starts with evidence instead of guesswork.