The bug-report workflow that keeps context intact.
Text-only bugs fail for predictable reasons: the repro steps are incomplete, the wrong window is visible, or the clip is too large to throw into Linear, GitHub, or Jira without a cleanup pass. Recorder is useful when you need to capture the exact state, the exact input, and the exact moment the app goes sideways before your train of thought disappears.
Frame the failing app, not your whole workspace.
Use drag-to-select when you want only the broken pane, or switch to window capture when the app itself is the boundary that matters. Either way, the report stays focused on the bug instead of exposing your IDE, chat sidebar, or everything else currently open on your desktop.
Use the countdown to stage the bug trigger cleanly.
The 3-2-1 overlay buys you a few seconds to put the app into the unstable state before the recording begins. That matters for bugs that only appear after a hover, a drag, a modal open, or a particular playback position, because the clip starts on the action instead of on frantic setup.
Make the repro inputs visible, not implied.
Click highlights and on-screen keystroke overlays remove the usual ambiguity around what you actually pressed. That turns a vague note like reproduce by opening preferences and hitting the shortcut into a clip where the engineer can see the exact click path and the exact keyboard sequence that caused the failure.
Trim, share, and attach before the context switch.
When you stop, Recorder opens the post-recording sheet with Save, Trim, Share, Reveal in Finder, and Delete. That is the useful moment for bug reporting: cut the dead air, keep the eight seconds that matter, then move the clip into the issue while the reproduction details are still fresh in your head.
