One-click GitHub issues

Configure the destination once. After that, a finished recording becomes a GitHub issue with one action: summary, protected report link and all.

Uses your own account, or a Proofline connection in preview.

An editable issue draft explains the discount-total bug with reproduction steps, expected and actual results, the reporter’s annotation and a File issue button.
Standalone development build, before the Proofline connection. Fictional checkout and sample report.
Needs
A fine-grained GitHub token per repository and protected publishing, or a Proofline connection
Optional
An AI model to write the summary
Help
Connect a repository

What happens when you file

  1. Stop the recording

    The report opens with File issue in the header and the editable draft above the evidence.

  2. Choose File GitHub issue

    The extension checks the repository, prepares the summary if a model is configured, publishes the report, and creates the issue with a link to it.

  3. Open the issue

    When it finishes, the issue opens. Later, the report shows View issue instead.

A full-page progress view shows the current stage and has Cancel. Cancelling stops further work and keeps saved drafts and deployments. It cannot undo an upload or issue request that GitHub or the report host already accepted.

Several repositories

Add as many repositories as you file into, each with its own token scoped to that repository with Issues: Read and write. Saving checks access to each one. The arrow beside File issue picks the destination; new reports remember your last choice, and an existing draft keeps the repository it was started for.

Through the Proofline GitHub App

With a Proofline connection (preview), issues are filed through the Proofline GitHub App on the repositories where your organization installed it, so you do not create or store a token per repository. The issue links to a Proofline hosted report instead of a Cloudflare deployment.

Avoiding duplicates

If the network fails after GitHub may have received the request, the extension does not post again automatically. Check GitHub issue looks for the earlier request first, and a retry reuses the existing deployment instead of uploading again.

Who can see what

Prefer another tracker? Use Publish report only for a protected link, or export a ZIP and attach it anywhere.

Record your next bug instead of describing it

Session Recorder is free and open source under the AGPL-3.0. Recording and ZIP export need no account. AI, transcription and publishing are optional: use your own providers, whose charges apply, or use credits with the optional Proofline connection preview when it reaches your installed version.

Get started with Proofline