Skip to content

GitHub Issues bug reports with the screen recording, console and network logs

Updated

GitHub Issues is where many product teams and open-source projects track bugs, right next to the code. Midge lets anyone on the team record a bug with its console logs, network requests and device info, then click Send to GitHub 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

  1. Install the app once. A workspace admin opens Settings › Workspace › Integrations in Midge and clicks Connect on GitHub. GitHub asks them to install the Midge Bug Reports app and choose the repositories it can open issues in. Midge checks with their GitHub sign-in that the installation is theirs before keeping it, then they pick the repository bugs go to.
  2. 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.
  3. Send to GitHub. On the report, click Send to GitHub. The issue is opened by the app, and the report shows the issue it created.

What the GitHub issue contains

GitHub renders Markdown, so the issue is readable without opening anything else:

  • a link to the Midge report with the video, console and network panels,
  • the AI summary,
  • numbered steps to reproduce, drafted from what you did in the recording,
  • the likely cause,
  • 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.

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.

Least access

The Midge Bug Reports app asks for issues: write and metadata: read, on the repositories you pick, and nothing else. It can't read your code, pull requests or Actions, and you can remove a repository or uninstall the app from GitHub's settings at any time.

Secrets stay out of your repository

Public repositories make issue text public. 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 issue is written from those redacted logs. The recording itself stays in Midge with its own sharing setting: "Workspace members" or "Only me" keeps it private even when the issue is public. See redaction.

From the issue to the fix

A developer opens the issue, clicks through to the recording, and sees the failing request and the stack trace at the moment the bug happened. If they work with a coding agent, the same link goes into Claude Code or Cursor, and the agent reads the console, the network requests and the steps through Midge's MCP server.

Who uses it

  • Small product teams that track everything in GitHub and don't want another tool for bugs.
  • QA and support filing bugs into the repository the engineers already watch.
  • Maintainers who want reports with the logs attached instead of "it doesn't work" issues.

Without the integration

Every report also has a link that's copied when you create it. Paste it into any issue, pull request or discussion and it opens the same report.

Related

Midge is free, including the GitHub integration: unlimited recordings, videos up to 15 minutes, and no watermark.

Frequently asked questions

What access does the Midge GitHub App have?
Issues: write and metadata: read, on the repositories you choose when you install it. It can't read or change your code.
Who appears as the author of the issue?
The Midge Bug Reports app. The issue links to the Midge report, which shows who recorded it.
Does it work with private repositories?
Yes, on any repository the app is installed on. Remember that the issue links to the report; set the report's sharing so the right people can open it.
Does it support GitHub Enterprise Server or GitLab?
No, only GitHub.com. A signed webhook can open issues elsewhere through your own small service.