Features / Capture & fix
Bug capture
The whole story, attached automatically
Your customer clicks the thing that is broken and Tore pins it. The report arrives with the replay, the console, the network trail, the browser and the exact element, and it tells them, in plain words, what it stripped out before sending.
Customer reportCheckout throws a 500 with no plan selectedreplay, console, network attached
It lands in your trackerLinear · Jira
fix/checkout-500Awaiting reviewMarketing dashboard
OverviewCampaignsReportsVisitors
48,210
▲ 12%
Signups
1,329
▲ 8%
Revenue
$92.4k
▲ 5%
The same widget has a second mode, “Suggest an edit”. A wording change comes back to your team as a one-line content change rather than a ticket.
Without it
Every bug report starts as a guessing game
Two replies spent asking what browser they were on
The ticket says “the export button is broken.” You ask which browser, which page, what they clicked, whether there was an error. They answer the next morning, from a phone, with a photo of their screen.
It works on your machine and you have no idea why
You open the same page, click the same button, and it works. Now you are guessing at their extensions, their tenant, their data, their network. The bug is real and you cannot see it.
A one-word wording fix costs a whole thread
Someone points out a heading says the wrong thing. It gets triaged, assigned, labeled, and sits in a backlog for a month, because the cheapest way to change three words is still a ticket.
How it works
They click the thing that is broken
Instead of describing it, the customer points at it. Tore pins the exact element, down to the selector (button#replace-headline), and they can draw, box, arrow, or blur anything else on the page before sending.
In the record
Pinned exactly, so nobody is guessing from a description.
Everything around that click is already attached
Console logs, network calls, a 30 second replay of what led up to it, the browser and operating system, and the element itself. The customer does nothing to make that happen and cannot forget to.
The number that matters
30second replay
Fixed by the product, not by whoever is on shift.
Secrets are stripped before upload, and they are told
Every input is masked before anything leaves their browser, and that is not a setting anyone can turn off. Password fields, embedded frames, canvas, video and audio are blocked outright, and you can add your own selectors. The panel then says “Removed 3 secrets before upload,” shows what is included, and asks them to confirm.
What they see
Removed 3 secrets before upload
If it is hard to reproduce, they record it
One click, in the page, nothing to install. Screenshot a crop, the visible area, or the full page, or record the screen, with an instant replay of the seconds before they hit record.
What that includes
- Screenshot a crop
- the visible area
- the full page
- record the screen
A second mode turns wording into a change, not a ticket
“Suggest an edit” lets them highlight text on the page and type the replacement. Tore records the original, the new text, and the element and route it came from, and prepares it as a one-line content change for your team.
What they see
Suggest an edit
What it means for you
The first reply is an answer instead of a question.
You open the report and you are already looking at the failure: the element, the console, the request that returned the wrong thing. Nobody has to be asked to try again while you watch.
The bugs you could never reproduce become watchable
A 30 second replay of their session settles arguments that used to take four days of back and forth. You stop needing the customer to be a good bug reporter.
Your customer is not handing over more than they meant to
They can see what is attached and they consent to it. That is a different conversation from asking someone to paste their console output and hoping there was no token in it.
The honest limit: Capture is a web SDK today. It runs in a browser, so a native iOS or Android app cannot use it yet; mobile crashes reach Tore through your crash reporter instead, and a mobile capture SDK is a later phase.