DarnlyClients and testers see your app with fresh eyes, which is why their bug reports are gold. They also write things like "the button thing on the main page is off again". Your AI agent can't do much with that. The trick is to make it easy for them to send the right details, and quick for you to pass them on.
1. Give them a template
Send this once and ask them to copy it for every bug:
Page: (copy the address from the browser bar)
What I did:
What happened:
What I expected:
Screenshot: (circle the broken part)
Browser and device:For the last line, send them to What browser am I using?. It copies their browser, system, screen size and dark mode setting in one click, so they don't have to know what any of that means.
If the bug is something that moves, like a menu that flickers, ask for a short screen recording. Video to GIF turns it into a GIF you can attach.
2. Ask for one bug per message
A list of twelve things in one email gets messy fast. One bug per message, or a numbered list with one screenshot each, keeps it clear for them, you and the agent.
3. Turn each one into an agent-ready report
Before pasting, spend thirty seconds on each bug:
- Try it yourself. If you can make it happen, copy the red console errors while you're there. See how to copy console errors.
- Separate the bug from the opinion. "The button is grey and does nothing" is a bug. "I don't love the font" is a design choice for you to decide on.
- Write the Expected line. Use their words if they're clear.
- Add the scope. "Only this page" or "everywhere". See why your agent asks if a change is local or global.
- Paste it with the screenshot. Into Claude Code, Codex or Cursor, one bug at a time or as a numbered list.
The guide on writing a bug report an AI agent can fix has a fuller template and examples.
4. Close the loop
When the agent says it's fixed, check it yourself, then tell the person who reported it. A quick "fixed, thanks" makes people far more likely to report the next one.
Using Darnly with testers
Darnly is a free Chrome extension, and anyone can use it, not just the person with the code. A tester adds it, skips the "link your project folder" step, and when they see a bug they press Option+Shift+B (Windows is coming soon), click the broken part and type what they expected.
Darnly then offers 1. Copy picture (the screenshot with the broken part boxed in red) and 2. Copy details (the page address, the element, and recent failed requests, plus console errors if they switched on Record errors on this site). They paste both into an email or chat to you, and you paste them into your agent. Passwords and card numbers are blurred in the screenshot, and tokens and keys in the details become [hidden], which matters when someone else's screen is involved.
Where Darnly isn't the right fit: if you have many clients who won't install anything, or you need bugs to go into Jira or Linear with comments and statuses, a team feedback tool with a widget on your site will serve you better. We compare one in Darnly vs Marker.io.