Bug reports your AI agents can fix.
Report bugs that tell the whole story, the first mile of every fix.
What a bug report usually leaves out
Writing a good bug report is hard. Even careful testers leave things out, and the fix waits while someone asks.
“I tapped something and it broke.” Which taps, and in which order?
By the time the report is written, the last 30 seconds are gone.
Text size, dark mode, language, network, battery. Nobody thinks to write them down.
A screenshot shows what went wrong, not which part of the app drew it.
What a bugsTweet report holds
The tester taps once and adds a note. The report fills in the rest.
- The picture, marked up, with private fields already blurred.
- The last 30 seconds: small pictures of the screen, plus the last 30 taps, in order.
- The phone and the app: settings, version, network, battery.
- Where it most likely lives in the code: the widget, its file and line, found by the widget's name.
- A test draft that replays what the tester did, ready for your agent to finish and prove the fix.
It all lands as a GitHub issue, ready for you or your AI agent.
Your code stays yours.
bugsTweet never gets access to your app's code. Reports go to a separate, private reports repository, and there the bugsTweet service allows only its own actions: post a report, comment, close or reopen, add a picture.
How it works
- Add bugsTweet to your Flutter app. One line. Your store app never contains it.
- Testers tap the logo. Mark up the screen, add a note, send.✓ Report sent
- You or your agent fix it. When the fix lands, the tester retests from the phone.