Every paid plan for Claude Code, Codex and Cursor has a usage limit. On busy days you hit it in the middle of building, and the agent stops. That's annoying, but it's also the best time to do the part of the work that needs you and not the agent: using your app like a real person would.
1. Don't spend the wait asking the agent to look
Agent browsers like Claude in Chrome or Codex for Chrome are great, but every page they open and every screenshot they take is part of the agent's work, so it uses the same limit. While you wait, you are the tester.
2. Click through your app like a user
Go through each main path: sign up, sign in, the main thing your app does, settings, and sign out. Try it narrow and wide. Type wrong things into forms. Our test-before-launch checklist has the full list.
3. Write each bug so the agent can act on it
For each problem, note four things: the page, the exact part that's wrong, what you expected instead, and any red errors in the console. A vague note like "the menu is weird" costs you a round of questions later. A template for a good report.
By hand, that's a screenshot, a note and a copied error for every bug. With Darnly it's Option+Shift+B, a click on the broken part and one line. It saves the screenshot with a red box, the element, the page and the errors from the last 60 seconds, and makes no AI calls, so it works fine while you're out of usage.
4. Keep them in one place
Put every bug in one list the agent can read: a BUGS.md in your project, or Darnly's inbox, which fills up as you capture. How to keep a list of bugs across projects.
5. When your limit resets, fix them in one go
Open your agent and hand over the list. With Darnly, type /darnly in Claude Code or Cursor, or say "fix my Darnly bugs" in Codex. The agent works through each report and tells you what it changed. If your plan has run out on one agent and you have another, the same reports work there too. More on switching agents.
Tip: if the agent can open a browser, ask it to check each fix on the page before it moves on. Darnly reports include a "How to check it's fixed" section for exactly that.
Want your waiting time to count? Add Darnly to Chrome, it's free. Or read why Darnly when your agent already has a browser.