Exports

You can export a project’s reports as a ZIP archive straight from the dashboard. The export is built to be handed to a coding agent or dropped into a repo: it’s a single Markdown file plus the captured screenshots and audio.

What’s in the ZIP

The download is named feedback.zip and contains:

• feedback.md — every selected report rendered as Markdown, one section per report, with a header summarizing how many reports are included.
• screenshots/ — the screenshot and audio files referenced from feedback.md, named so each one links back to its report.

Each report in feedback.md carries its status, channel, source URL, timestamp, and environment, followed by its text, any highlighted on-page selection, captured console errors, and links to its screenshots and audio. The Markdown is wrapped with a short instruction preamble so it reads cleanly as a brief for an AI agent.

Note

Reports are written newest-first, and a single export includes up to 500 reports. Narrow the export with the filters below if a project has more.

Filtering an export

The export can be scoped before it’s generated:

• Status — include only reports in one or more statuses (new, triaged, in-progress, closed).
• Channel — include only reports for a single channel, by its channelKey.

With no filters, the export returns the project’s most recent reports across all channels and statuses.

Access

1. The export is session-authed — you have to be signed in to the dashboard.

2. You must be a member of the organization that owns the project. A non-member gets a forbidden response.

This is the same access rule as the rest of the dashboard: organization membership grants access to every project in the organization, and the export honors that boundary.