Linear bug reports with the screen recording, console and network logs
Updated
Linear teams move fast, and an issue that says "checkout is broken" slows them down. Midge lets anyone on the team record a bug with its console logs, network requests and device info, then click Send to Linear to open an issue with the AI-written summary, the steps to reproduce, the likely cause and a link to the recording.
How it works
- Connect Linear once. A workspace admin opens Settings › Workspace › Integrations in Midge, clicks Connect on Linear, signs in and picks the team that triages bugs.
- Record the bug. With the Chrome extension, Midge for Mac or Midge for iPhone, record your screen or take a screenshot. The report gets the console, the network requests, your clicks and the device details.
- Send to Linear. On the report, click Send to Linear. The issue opens in that team, and the report shows the issue it created.
What the Linear issue contains
Linear renders Markdown, so the issue reads well on its own:
- Watch the Midge report: the link to the recording with its console, network requests and steps.
- Summary: what went wrong, in two or three sentences.
- Steps to reproduce: numbered, drafted from what you actually did in the recording.
- Likely cause: for example, a
500from an API call followed by an unhandled error. - Context: the page URL and the number of console errors and failed requests.
A note at the end says the summary was written by AI from the redacted logs, so whoever picks it up checks it against the recording.
Your words first
Whatever the reporter typed when they sent the report, such as the expected result or which account they used, goes into the issue right under the link, before the AI summary. The person who saw the bug gets the first word, and the summary fills in what they didn't write down.
Why it fits how Linear teams work
Linear works best when issues are small and clear enough to pick up without a meeting. A recording with the logs attached answers the questions that usually come back on a bug: which browser, which account, what did the network do, what was in the console. The engineer opens the link, watches 20 seconds, sees the failing request and starts on the fix.
For teams that use coding agents, the same link works there: paste it into Claude Code or Cursor and the agent reads the report through Midge's MCP server.
Secrets stay out of Linear
Midge removes passwords, tokens, cookies, authorization headers and card numbers from the logs before they leave the browser or the phone, and masks emails and phone numbers. The AI summary and the Linear issue are written from those redacted logs, so a token in a request header never ends up in your issue tracker. See redaction.
From customers, too
Support can send a customer a recording link. The customer records the problem in their browser without an account, the report lands in your Midge workspace, and Send to Linear turns it into an issue with the customer's own recording behind it.
Without the integration
Every report also has a link that's copied when you create it. Paste it into any Linear issue or comment and it opens the same report. The integration saves the copying and writes the summary for you.
Related
- All integrations: Jira, GitHub Issues, Slack and webhooks.
- Network logs and console logs: what the recording captures.
- Bug report template.
Midge is free, including the Linear integration: unlimited recordings, videos up to 15 minutes, and no watermark.
Frequently asked questions
- What access does Midge get to Linear?
- It reads your teams so an admin can pick one, and creates issues. It doesn't read existing issues or comments.
- Which team do issues go to?
- The one a workspace admin picks when connecting Linear. They can change it later in Settings.
- Does the issue include the video?
- It links to the Midge report, where the video plays next to the console and network logs. The issue itself carries the summary, steps and likely cause in Markdown.