Point at the element. Keep its HTML and CSS.

On the ticket

An inspector, attached to the report.

They can skip the picker. A report can be a screenshot, a replay, and a note. When they do pick a node, the bug has enough to find it in the code.

• A selector for that node

  BugTrap prefers a unique id. Otherwise it builds a short path from the tag and a couple of classes, and adds :nth-child when siblings would match the same path.

• The HTML

  The element’s markup is stored with the bug. Very long markup is shortened, and the ticket says when it was cut.

• Styles that actually differ

  Computed styles are compared with an empty element of the same tag. What comes back are the properties that differ, up to 200 of them.

• The rules that matched

  Up to 40 CSS rules the page is allowed to read, including adopted stylesheets and the shadow root that holds the element. The bug shows them next to the computed values.

Also included

The rest of the product.

• Screenshots and markup

  The page, and the marks on a second image.

• Session replay

  The last 30 seconds, with inputs masked.

• Console, network, and environment

  Logs, requests, environment, and your metadata.

• Chrome extension

  File from the page you are viewing.

• Forms for guests and members

  Different fields for visitors and teammates.

• The team queue

  Status, assignment, comments, and internal notes.

• Asana

  New bugs become tasks in a project you choose.

• Team and workspaces

  $5 a month. Admins, members, and guests.

• MCP for coding agents

  Read the queue from Cursor, Claude, or Codex.