3 in your folder ✦
an open-source chrome extension

what's the brief?

Talk through a bug.
Your agent writes the ticket.

Hit the toolbar, say what's broken, hit export. Your coding agent reads the capture and files a proper ticket.

Add to Chrome Star on GitHub
RIGHT NOW

Half the bugs your team see never get filed.

Writing a good ticket takes five minutes. So nobody bothers.

I see bugs every day. Filing tickets takes too long, so I just don't.
SR Sales repB2B SaaS
I try to file every bug I catch. I forget half of them by lunch.
F FounderSeed-stage startup
I have twelve bugs in my notes app. Zero in the tracker.
PM Product managerSeries B fintech
HOW IT WORKS

Three steps.
About thirty seconds.

Brief captures everything. Your agent does the writing. Your team actually files things. Engineering actually fixes them.

0:14

Record

Hit the toolbar. Talk through the bug while it's on screen.

brief.zip your agent

Export

Drop the prompt into Claude Code, Cursor, or any agent.

ENG-242 Ready
Real bug. Real fix.
videoscreenshotlogsreprocode

Ship

A perfect ticket lands in your tracker. Ready for a human or your AI to tackle.

WITH BRIEF vs WITHOUT

Same bug. Two tickets.

Ticket created with Brief
20sto write
✓attachment
✓console logs
✓repro steps
0follow-ups
vs
Ticket created by a human
5minto write
✕attachment
✕console logs
✕repro steps
3follow-ups
assignable to your AIfewer hallucinations structured for triageAI or human ships it no follow-up questionsengineer just ships it
ENG-242 Bug Ready
Checkout CTA overlaps order total on mobile (< 390px)
📋 Steps to reproduce
  1. Open the cart on a viewport ≤ 390px
  2. Proceed to checkout
  3. The "Place order" button renders over the total
⚠️ Actual

The button covers the order total, leaving it untappable.

✅ Expected

Button and total stack cleanly, with room to tap each.

🎥 video 📷 screenshot 🧾 console logs 📋 repro steps
💬 1 reply EM
Em (engineer) 2 min ago

Crystal clear. Picking it up now, thanks ✨

AI hallucinates the fixno context vague, no specificsno screen, no repro more questions, more frictiondays of back-and-forth
ENG-241 Frontend Backlog
Investigate potential checkout experience issue

This ticket tracks investigation of a potential issue that may affect the checkout experience. Users may, under certain circumstances, encounter unexpected behavior.

Acceptance criteria: relevant elements behave as expected. Further details to be gathered during triage.

✕ no video ✕ no screenshot ✕ no logs ✕ no repro
💬 3 follow-ups EM
Em (engineer) 5 min ago

Which page is this on?

What was the user trying to do?

Can you share repro steps + a screenshot?

WATCH

Watch a bug become a ticket.

Watch demo.

ready?

Add to Chrome →