Skip to content
Screen Recording

From recording to written guide, bug report, or agent handoff

A video is not always the only thing your audience needs. A new admin following an onboarding tutorial wants a checklist with pictures they can skim at their own pace. An engineer or a coding agent triaging a checkout failure needs the exact steps, the console error frame, and a clear line between what happened and what you think caused it.

Screen Recording turns your recording into structured written deliverables and gives both its built-in agent and your own coding agents direct, permissioned tools to work on the package.

Illustrated step-by-step guides

Open the Steps tab in the inspector and choose Write a Guide (or build steps by hand). Screen Recording reads your transcript and the logged clicks, keystrokes, and window switches to produce a concise, numbered walkthrough.

  • Rendered frame for every step. Each step includes a still frame rendered from that exact moment in the recording (respecting your recording's crop, unzoomed and without captions) with a focus ring marking where you clicked.
  • Silent demonstrations included. Because every click and control label is logged during capture, steps are generated even for passages where you worked in silence.
  • Flags what was never shown. If you mention something in narration that never appears on screen, such as an invitation email or a settings page you did not open, the guide lists it under Not Shown in the Recording rather than inventing a step for it.
  • Respects your edits and covers. Cutting or replacing a passage shifts downstream step timestamps (Writeup.shifted) so you or your agent can remove replaced steps and add new ones in the Steps tab (or via writeup_write), and any privacy cover is applied to every step picture and line of text.

Structured bug reports

Choose Write a Bug Report in the Steps tab to turn a narrated or silent repro into an actionable defect report.

  • Observed, Expected, and Possible Cause. The report keeps what the recording shows (Observed) and what should have happened (Expected) separate from any guess at the underlying defect (Possible Cause), which is explicitly marked as an inference alongside the evidence that supports it.
  • Keeps the baseline that works. When your recording shows a working purchase first and a failing discount code second to isolate the bug, the report preserves both attempts and explains why the contrast matters.
  • Export anywhere. Export any guide or bug report as a self-contained HTML page, a paginated US Letter PDF, or Markdown with a step-images folder beside it. You can also click Copy as Markdown to place the Markdown text (with local file paths to the rendered step pictures) on your clipboard; when pasting into web trackers like GitHub, Linear, or Jira, upload the step pictures separately or export self-contained HTML or PDF when you want the pictures bundled in one file.

Screen Recording Agent in the editor

Click Agent in the editor toolbar (or press Option-Command-A) to open Screen Recording Agent in the inspector column.

Start with a one-click job (Finish a Demo, Write a Guide, Write a Bug Report, or Remove Filler Words) or paste your own brief, such as "Make a polished vertical demo, follow the important clicks, and leave keystrokes hidden." The agent inspects the transcript, action log, and contact sheets of rendered frames, and applies its changes through the editor's tools. Every change is a named undo step, so you can review or undo any decision with Command-Z.

Screen Recording Agent runs on your Plus One credits by default, or you can configure your own API key in Settings › Agents › Advanced.

Local MCP server for Claude Code and Codex

Screen Recording also hosts a local Model Context Protocol (MCP) server on a private Unix socket on your Mac. Connect your coding agent with a single command (shown in Help › Connect Agent… and Settings › Agents).

claude mcp add screenrecording --scope user -- '/Applications/Screen Recording.app/Contents/Helpers/screenrecording' mcp
codex mcp add screenrecording -- '/Applications/Screen Recording.app/Contents/Helpers/screenrecording' mcp

When an external agent connects, Screen Recording prompts you in a floating panel to approve access for a single recording or a folder, and you can revoke access at any time in Settings › Agents.

Once approved, your agent can call more than 35 structured tools to list and search recordings, read transcripts and action logs, inspect contact sheets, render full-resolution cropped regions of error consoles (frame_render), cut words and actions, apply styles and camera layouts, scan and cover private details, write guides and bug reports, create clips, and run exports. See recording for coding agents.