Bug reports for teams and agentsPrivate beta

Bug Dossier.

From “I found a bug” to the fix.

Bug Dossier is the product I’m building now. Record the tab where something broke and file it from the page: the bug arrives with its video and DOM replay, console, requests with their bodies, and storage, all on one timeline. Your team replays it in its own workspace, and your coding agent reads the same evidence over MCP and posts what it found.

Explore Bug Dossier Get early access Add to Chrome

The launch filmLaunch film · 1:18 with voiceover and English captions. Stand-in people, a sample shop and Bug Dossier’s own interface.

01 / 07

Read the film’s transcript

Every bug starts as one message. A new bug report, every three minutes. Every team has this channel.

A feature hits QA, and every bug gets written up by hand. A thread. A sheet. A ticket. No QA? Then it's you, digging.

Someone reports it. QA can't reproduce it. Third try, it's on video. Then the developer's questions start. And it works on his machine. Four days. Nobody has started fixing it.

What if the bug report carried everything? Meet Bug Dossier. Here's how it got fixed. You just record, point at what's wrong, add a note, and submit. Dev, QA or production. Every answer's already there. One link. Everything in it.

And what if you didn't have to dig at all? Your coding agent reads the dossier, and tells you what broke, what changed, and why. Then it posts the fix.

No more back-and-forth with QA. No sheets. No threads. No digging.

Bug Dossier. We're dropping the beta. Get early access at bugdossier.com.

THE STORY

Why this exists.

The problem

Most bugs arrive as a message and a screenshot. Then the questions start: the steps, the browser, the console, the request that failed. QA can’t reproduce it, the developer can’t either, and a report can wait days before anyone starts on the fix.

The approach

Capture the evidence once, while the bug is being reproduced. The recorder keeps the replay, console, network and storage on one clock, and you file the bug from the page where it broke. People open the dossier in their company’s workspace; coding agents read the same dossier over MCP and can do what their person can.

The useful parts.

What the product brings into one place.

Record the tab, mark what matters

Click the toolbar icon or press ⌘⇧U. A small bar waits in the corner while you reproduce the bug: flag a moment, pick an element, draw on the page, take a screenshot or leave a note.

File it from the page

Press Stop and a filing card opens right where you are: title, note, environment and tags. Submit sends the bug to your workspace with everything attached.

Everything needed to debug it

Video and DOM replay, the console with its stacks, requests with headers and bodies, cookies, storage writes and app state, on one timeline. Other sites’ sign-in cookies never leave your browser.

Your agent can do what you can

One command connects Bug Dossier to the coding agents on your computer, such as Claude Code, Codex and Cursor. Approve it once with your work Google account; everything an agent writes says which agent wrote it.

From start to outcome.

Walk through the product, one step at a time.

STEP 01 OF 04

Join the beta

Leave your work email at bugdossier.com; your company gets its own workspace when you are invited. Add the recorder from the Chrome Web Store and sign in.

WHAT THIS GIVES YOUA recorder connected to your team’s workspace.

Behind the build.

Decisions, boundaries, and the current state of the work.

The Chrome recorder is published on the Chrome Web Store (version 1.0.2), and filing a bug needs a Bug Dossier workspace. Teams are being let in a few at a time: leave a work email on the beta page for an invite.

Take a closer look.

Open the product or explore its source material.