Record the bug. Point at it. File the issue.

One path from bug to issue

Configure your integrations once. After that, filing is a single action on a finished recording.

1. Record

   Reproduce the bug in Chrome. Clicks, typing, console errors, network requests and screenshots go onto one timeline, including tabs the app opens. Browser recording

2. Annotate

   Turn on Annotate, click an element or drag a rectangle, and say what is wrong. Numbered pins lead the report. Live annotations

3. File

   Choose File GitHub issue. A model writes the summary, the report publishes behind a login, and the issue opens with a link. GitHub issues

Useful on its own. Optional Proofline connection.

Nothing here requires an integration. Each one you add removes a manual step.

Works without any account

Stays in your browser until you export it.

• Interactions, console and network capture
• Live annotations and screenshot markup
• Screenshots and tab video
• Local storage and capture-time redaction
• ZIP export for people and coding agents

With your own accounts

Configured once; data goes directly to the service you choose.

• AI issue summaries and session names
• One-click GitHub issues, several repositories
• Reports on your Cloudflare Pages, behind Access
• Voice note transcription

With Proofline (preview)

Connect a Proofline account when you would rather not manage providers. AI summaries, session titles, page vocabulary and transcription use Proofline credits. Reports are hosted privately for your workspace, and issues go through the Proofline GitHub App. Proofline grants 10,000 credits once, after your organization completes onboarding and installs the GitHub App. How the Proofline connection works.

Evidence you can share with care

Authorization headers, cookies, token-like fields, sensitive URL parameters and password inputs are masked before anything is stored. Redaction is pattern-based and does not read screenshots, video or audio, so review a report before it leaves your team. Published reports require sign-in, and API keys are never written into exports or reports. How privacy and redaction work.

Compared with hosted bug tools

Jam, Marker.io, BugHerd, Userback and BrowserStack Bug Capture offer shared workspaces, client feedback, broad integrations and team administration. Session Recorder is narrower: free, open source, GitHub-first, and run on accounts you already control. Read the comparisons, including when each tool is the better choice.

Hand bugs to coding agents

Exports are Markdown with a shared clock across every event, sized to fit a context window. The guides show how to use them.

• With Claude CodeUnzip the report in the repo and point Claude Code at it.
• With CursorAttach report.md to Cursor’s Agent.
• With CodexGive Codex the browser evidence it cannot collect itself.
• With ChatGPTUpload one report instead of screenshots and log fragments.
• Example reportA complete report.md, recorded against test data, as an agent receives it.