Skip to content

Recording links: your customers record the bug, nothing to install

Updated

Some bugs only happen on a customer's computer. Asking them to install a browser extension, or to describe what they clicked, rarely works. A Midge recording link asks for nothing: you send a link, they record their screen in the browser and press Send, and the recording arrives in your workspace as a report.

How it works

  1. In Midge, open Settings › Workspace › Recording links, give the link a title and, if you want, a short note ("Open the checkout, try to pay and record what happens").
  2. Send the link to your customer: by email, in a support chat, in a ticket.
  3. They open it, click Start recording, choose a screen, window or tab, and do what went wrong. Their voice is recorded too if they allow the microphone.
  4. They watch it back, add their name, email and a few words if they like, and click Send.

The recording shows up in your workspace with the title "Ada via Show us the bug", who sent it and how to reach them. Like any Midge recording it gets a transcript, an AI summary with steps to reproduce, and it can go to Slack, Jira, Linear or GitHub.

Built for support teams

  • No account, no install. The link works in any modern desktop browser.
  • Private by default. Recordings from a link can be opened only by your workspace.
  • Safe to share. A link is long and unguessable, protected against bots, and limited to 50 recordings a day. Turn it off when you're done.
  • One link per purpose. Make one for your help center, one per big customer, one per release; each counts what it received.

When a link beats the extension

The Chrome extension and Midge for Mac are the best way to report a bug when you or your team found it: they attach the console logs and network requests of the page, the clicks that led there, and remove secrets before upload. A recording link is for the other side of the support desk: the customer who hit the bug, on their machine, with their data, who will never install a tool for one report.

Typical uses:

  • Support chats and tickets. Instead of a back-and-forth about which button they pressed, paste the link and ask them to show it. The video answers the questions before you ask them.
  • Beta programs. Give each beta group a link in the release notes, so feedback arrives as recordings instead of screenshots of screenshots.
  • Sales and onboarding calls. When a prospect says "it didn't work for me", a link turns that into something an engineer can watch.
  • Bug bounties and community reports. Ask reporters to attach a recording through a link made for that program.

Inside your own app: the website SDK

Add one script tag and your app gets a Report a bug button that opens the same recorder, without leaving the page. Because it runs in your app, the report also carries what the page did while the customer recorded: console errors, network requests, clicks and page changes, all redacted in their browser. Midge.metadata() adds your own context, such as the user ID, plan or feature flags, and elements marked data-midge-blur are blurred in the video. It only sends from domains your workspace has verified. The website SDK guide shows the setup.

What happens after they press Send

The recording is processed like every other report. Midge writes a transcript of what they said, then an AI summary with the steps to reproduce and the likely cause, from the video's transcript and their description. If your workspace posts new reports to Slack or a webhook, this one goes there too, so the right person sees it without checking a dashboard. From the report page anyone in the workspace can open a Jira, Linear or GitHub issue with one click; see integrations. Coding agents can read it over MCP.

Privacy

Nothing is recorded until the customer clicks Start and picks what to share, and nothing is sent until they click Send. They see your workspace name before they start, and the page tells them who will see the recording. Their name and email are optional. The recording is visible only to your workspace; to remove it, delete it like any other report. The privacy policy has the details.

Recording links are free, like the rest of Midge: unlimited recordings, up to 15 minutes each, no watermark.

Frequently asked questions

Do my customers need an account or an extension?
No. They open the link in Chrome, Edge, Firefox or Safari on a computer, share their screen, record and send. Their name and email are optional.
Who can see what they send?
Only your workspace. Recordings that come through a link are visible to workspace members, not to anyone with the link, and the person who sent it can't open it again.
Is there a limit?
Each recording can be up to 15 minutes. A link takes up to 50 recordings a day, and you can turn a link off or delete it at any time.
Do recordings from a link get console and network logs?
Not from the link page: a browser page can't read another site's logs, so they get the video, the customer's voice if they allow the microphone, a transcript and an AI summary. Put the same recorder in your own app with the website SDK and its reports carry the page's console, network requests, clicks and your metadata.