How to report a bug to Lovable (with a screenshot)

Lovable builds fast, and it fixes fast too, when it knows exactly what you mean. "The button is broken" makes it guess. A marked picture and one clear sentence usually don't.

Step by step, by hand

1. Make the bug happen once more. Note what you clicked, in order.
2. Take a screenshot and mark the broken part. Lovable's chat lets you attach a picture and click Draw to mark it up before you send.
3. Add it to the chat. Paste it, drag it in, or use Attach files in the Chat actions menu.
4. Say what you expected. One sentence. "The Sign up button should open the form, like the one in the header does."
5. Say how far the fix should go. "Only this page" or "every page". It saves a round of questions.
6. Add the clues a picture can't show. If nothing visible happens, open the browser console (Cmd+Option+J on a Mac, Ctrl+Shift+J on Windows) and paste the red lines. See how to copy console errors.

Lovable's own Select elements

Inside the Lovable preview, the Select elements tool in the preview toolbar lets you pick an element and describe the change. For tweaks while you build, that is the quickest route. It only works in the preview, though. Bugs you find on your published site, on your phone, or while testing a real sign-up still need a screenshot and a note.

The one-key way with Darnly

Darnly is a free Chrome extension that makes the screenshot and the note together, on any page, including your published Lovable site. Press Option+Shift+B (Windows is coming soon), click the broken part, type what you expected and press Enter.

Then click 1. Copy picture and paste it into Lovable's chat, and 2. Copy details and paste that too. The picture has the broken part boxed in red with your note on it. The details hold the page address, the element's text and styles, and failed requests from the last 60 seconds, plus console errors if you switched on Record errors on this site. Passwords, card numbers, tokens and keys are hidden before anything is copied.

Darnly doesn't make Lovable smarter. A good screenshot and sentence often get the same fix. What it saves is the hand-over: one key instead of screenshot, crop, mark, find the console, copy, paste. See Darnly vs a plain screenshot.