Keep the report in the project
Cursor’s Agent documentation describes code edits and tool use. For a repeatable handoff, request a Markdown report with the goal, files changed, checks run, their results and unresolved items. Save it in a sensible project folder rather than copying a fragment of chat with no path back to the code.
The fictional Agent Review Pack includes report.md. Open it beside its plan and checklist. For each statement such as “the feature is complete,” identify the changed file or observed result that supports it. If the report lacks a verification step, record that gap instead of silently treating the narrative as a test.
Separate reading and editing
You can read the file in Cursor’s editor, use the free online reader for one file, or use a desktop reader for the whole folder. Aero Markdown is designed to keep a rendered page, file tree and heading outline separate from the coding editor. Its optional Cursor hook can open newly written Markdown after setup; the already open file can reload on disk changes. These are distinct behaviors, and neither proves report accuracy.
This is a workflow guide based on a fictional report, not a measured productivity comparison or a recorded Cursor session. The Mac app remains unavailable to download. For exact reload behavior, see reading agent-written Markdown.