DarnlyWhen you build several things with AI, bugs pile up in odd places: a note on your phone, a message to yourself, a screenshot on the Desktop called Screenshot 2026-11-02 at 09.14.png. A week later you can't remember which app it was for, or what was wrong. A list fixes that, and the right kind of list lets your agent work through it for you.
Option 1: a BUGS.md file in each project
Make a file called BUGS.md at the top of each project. One bug per line, with a checkbox:
# Bugs
- [ ] /settings: Save does nothing. Expected: saves and shows "Saved".
- [ ] /pricing: Subscribe button grey. Expected: blue like Start trial. Only this page.
- [x] Home: logo too big on phones. Fixed: max width 160px in Header.Why this works well with AI agents:
- It lives with the code, so the agent can read it. Say "fix the open bugs in BUGS.md and tick them off".
- Each line already has the page and the Expected part, which is what agents need most.
- Ticked lines show what was done, so you can check the fixes later.
Keep screenshots in a bugs/ folder next to it and mention the file name on the line. If the screenshots show private data, add that folder to .gitignore. The .gitignore generator can help, and the Markdown preview shows how the file looks.
Option 2: one note for everything
If you'd rather have one place, use a single note with a heading per project. Put the project name and address on every bug. When you sit down to fix, copy that project's section into your agent's chat. This is easier to add to from your phone, but the agent can't read it on its own.
Option 3: a tracker
GitHub Issues, Linear or Trello are worth it when other people report bugs or share the work. For one person, they add steps between "I saw a bug" and "my agent fixed it". If you already use one, keep using it.
Habits that keep the list useful
- Write it down when you see it. Not later. The details fade fast.
- One bug, one line. Split "the checkout is weird" into the actual things.
- Always include Expected. See how to write a bug report an AI agent can fix.
- Fix in batches. Five small bugs in one sitting is faster than five sessions.
- Check what was fixed. Look at the page yourself before ticking it off.
Let the list fill itself with Darnly
Darnly is a free Chrome extension that turns "write it down when you see it" into one key. Press Option+Shift+B (Windows is coming soon), click the broken part, say what you expected. Each bug becomes a markdown file and a PNG screenshot in that project's .darnly/inbox/ folder, with the page address, the element and recent errors.
That folder is your list. The Darnly panel shows how many are waiting and how many are fixed. When you type /darnly in Claude Code or Cursor (or say "fix my Darnly bugs" in Codex), it works through the inbox, adds a Fixed: line to each report saying what it changed, and moves it to .darnly/done/. Darnly shows you "1 bug fixed. Take a look." with that line, even if the panel was closed while the agent worked, so checking is quick. If the agent needs to ask you something, the bug says "Your agent is waiting for your input" instead of just looking stuck.
Darnly remembers which project each site belongs to, so bugs from your second app land in that app's folder, and a bug you no longer need goes with the × next to it. Working on projects in the cloud, or on more than one machine? The optional cloud inbox is an MCP server for bug reports: it keeps bugs from all your projects in one private list. Your agent reads it through Darnly's connector at https://api.darnly.dev/mcp, and is told to only fix the bugs whose page belongs to the code it's working on. You sign in with Google to use it, and fixed bugs are deleted 30 days after they were fixed. How to connect your agent.
For Mac apps, the iOS Simulator and the Android Emulator, the Darnly Mac app saves to the same .darnly/inbox/ folder, so one list covers web and app bugs. Get it from darnly.dev.