BUGRELAY / THE CONTEXT LAYERCAPTURE → REVIEW → RELAY

WHAT’S NEW A closer review. Better tools.

BUG REPORTING, WITH THE MISSING CONTEXT

Stop guessing.
Start with evidence.

Turn “something’s broken” into a report your developer can act on. Screenshots, video and diagnostics—reviewed, connected, and ready for your team.

Start capturing bugs See how it works

Private by defaultReview before uploadBuilt for agencies & teams

THE REPORT IS ONLY THE BEGINNING.INTERACTIVE PREVIEW / SAMPLE DATA

BStudio workspace /Evidence room

Private workspaceAB

BR—024 / REVIEWED EVIDENCE

Checkout doesn’t finish

High priority

checkout.example / payment

STUDIO SUPPLYMenu ☰

A SPACE FOR GOOD IDEAS

The everyday desk kit.

Considered essentials. A better workspace.

ORDER TOTAL$249.00

Complete checkout1

Something went wrong. Please try again.

Reviewer

Reviewed before uploadVisual evidence + selected diagnostics

01 / CAPTURE02 / REVIEW03 / RELAYTake a closer look

Ready to hand offEvidence reviewed · Sample report

From the person who spots it.To the person who can fix it.

EVERY REPORT, A CLEARER PICTURE

Less explaining.
More fixing.

The screenshot shows where. The video shows how. Diagnostics help your team understand what happened.

SCREENSHOTS

Mark the exact spot.

Pin the issue, draw an arrow, add a note, or crop the screenshot. Use an opaque mask or selected-area blur before sending.

VIDEO

Show the whole interaction.

Record a short screen video, review the clip and attach it to the same report. Sharing begins with your browser’s explicit permission.

DIAGNOSTICS

Keep the useful diagnostics.

Include bounded console errors, fetch/XHR metadata, page URL and browser context. Filter out events you don’t need.

TEAM TRIAGE

Give every issue a home.

Organize by workspace and project, assign a teammate, add labels and discuss reproduction steps next to the evidence.

PRIVACY CONTROLS

Review before you relay.

Common secret patterns are filtered from diagnostic text. Screenshots and video need your review. Private evidence uses authorized access.

SHARING

Share the right amount.

Create revocable, expiring report links or send selected fields to configured tools. Choose a visual-only share when logs aren’t needed.

A SHORTER PATH TO REPRODUCIBLE

Spot it. Show it.
Relay it.

Explore the workflow

01
Capture
Start on the website where the issue happens. Take a screenshot or record a short video.
02
Review
Add reproduction steps, connect a pin to a diagnostic, and remove anything you don’t want to send.
03
Relay
Upload to your private workspace. Assign it, discuss it, or share a scoped link.

01 / BUILT FOR THE HANDOFF

A report worth
opening.

All the pieces of the issue. One place to understand them.

Meet your next bug report

BR—024

The final step
shouldn’t be a dead end.

● Needs attention

The exact spot

An annotated screenshot, with the issue in focus.

The full interaction

A reviewed clip of the steps that led here.

The useful signals

Selected diagnostics, beside the visual context.

The next move

An assignee, a discussion and a clear status.

Private workspace · deliberately shared

FOR THE PEOPLE ON BOTH SIDES OF THE ISSUE

Different roles.
Same clear picture.

From the first client review to the final release check.

01 / AGENCIES & CLIENTS

Make feedback actionable.

Give every client website its own project. Keep feedback, visual evidence and the next conversation together.

Built for your handoffs

02 / DEVELOPERS

Start with context.

See the steps, inspect selected console and network events, and connect the report to a configured GitHub repository.

Explore the evidence

03 / QA & PRODUCT

Keep the review moving.

Capture a broken interaction, assign the report, and follow its status through the team’s workflow.

Follow the workflow

Your websiteReviewed capture

BBugRelayCONTEXT, CONNECTED.

GitHub issuesEmail notifications

Available with configured integrations and selected delivery.

LESS COPYING. A BETTER HANDOFF.

Keep the context.
Move the work.

Your report is the starting point. Connect GitHub and email, choose the details to include, and track delivery from the workspace.

Explore integrations

CONTEXT IS USEFUL. CONTROL IS ESSENTIAL.

A little more deliberate.
A lot more considered.

Choose when capture starts, review what goes out, and decide who gets to see it.

Explore security & privacy

You press start.

Explicit capture. Visible recording state. A clear stop control.

You review the evidence.

Select diagnostics. Mask screenshot pixels. Approve video separately.

You choose the audience.

Private reports, project permissions and expiring, revocable links.

A GOOD PLACE TO START

Less setup mystery.
More first-report energy.

THE FIRST REPORT

From toolbar to team.

Install the beta, connect a project and make your first reviewed report.

SHARE WITH INTENTION

The right link. The right context.

Understand private access, visual-only shares and revocation.

PRODUCT NOTES

See what’s taking shape.

Follow the changes to capture, review and your reporting workflow.

A FEW THINGS TO KNOW

Questions before your first report?

Does BugRelay record automatically?

No. You explicitly start each capture. Screen video also requires choosing a surface in your browser’s sharing prompt.

Does it collect passwords or request bodies?

The diagnostic collector excludes request bodies, headers, cookies and storage contents. Common secrets in diagnostic text are filtered. Visible screenshot/video pixels still need your review.

Can I blur sensitive content?

You can blur a selected screenshot area or cover it with an opaque mask. Use a mask for full concealment. These tools do not redact video frames.

Is the extension in the Chrome Web Store?

The current extension is a private beta distributed by workspace administrators. The Help page explains the unpacked installation process.