Widget: Capture
What reporters see first, report types, markup tools, and automatic evidence like session replay.
Widget → Capture decides what reporters see first, how they mark things up, and which evidence is attached automatically.
What reporters see first
Pick a start mode. The options depend on the widget design (the switch in the Widget tab's toolbar).
| Start mode | What happens |
|---|---|
| Elements first | Reporters click what's wrong on the live page, then describe it. Your agent gets selectors, not pixels. |
| Form first (recommended) | Reporters describe the problem first. They can point at elements, or add a screenshot, from the form. |
| Type first | Reporters choose Bug, Idea, or Question, then fill in the form. Needs Studio. |
How the element picker works
- A bar at the bottom of the page lets the reporter click up to 8 elements. The bar
says Skip until something is picked, then Done. Skip and
Escboth open the form. - The picker is an overlay, so it doesn't change your page. The only mark left in the DOM
is a
data-snagrelay-pickattribute on picked elements. - Clicks on the page are swallowed while picking, so your site's own handlers don't fire. Hover menus and tooltips stay open, so their contents can be picked.
- Picked elements become the report's affected elements, with selector, text, and page location.
- Not covered: cross-origin iframes and canvas apps. Use a screenshot there.
Evidence tray. Console output, failed requests, a page snapshot, and the session replay are attached silently. The form only shows a screenshot the reporter marked up, and they can remove it.
| Start mode | What happens |
|---|---|
| Screenshot first | Opens the annotator on a screenshot. Good for client sites. |
| Form first | Describe first. The screenshot is optional. |
| Type first | Choose Bug, Idea, or Question, then the form. Needs Studio. |
New projects start on AI context and Form first. Elements first is opt-in, because landing straight in pick mode can confuse a first-time reporter. Switching a project to Visual report moves an Elements first setting to Form first.
Report types (Type first)
(Studio and Agency.) With Type first selected, a list of types appears. Click Add a type to create one:
| Field | What it does |
|---|---|
| Title | The button reporters see, such as "Bug", "Feature request", or "Question". Up to 50 characters |
| Description | A short line shown under the title. Up to 200 characters |
| Title prefix | Added to the report's title, such as Bug: or Question - |
| Target column | The tracker column new reports land in. None uses the project default |
Each type has a switch to show or hide it, plus edit and delete. Types let one project send bugs, ideas, and questions to different columns of the same tracker.
Markup tools
For when a reporter adds a screenshot. Toggle each tool on or off:
Highlight, Comment, Pen, Arrow, Hide (to cover private details), and Screen recording (Studio and Agency). Set the Marker colour used by the pen, arrow, and highlight.
Screenshots are a paid feature
Screenshots and markup are part of paid plans (Solo and above). Free reports carry the element, errors, console, network, and replay without a rendered screenshot. See Plans & Limits.
Attached automatically
Session replay records what happened on the page before the report. How long it keeps depends on your plan (30 s, 60 s, or 3 min). Turn it off here if you don't want it. See Session replay.
Next: Form.