The best bug report we ever received
Today a customer emailed about links in his wiki: citation links from his reference manager rendered fine, but clicking them did nothing. Attached was a bug report — and it was the best one we've ever received.
It had a one-line summary. Exact app version, build, and bundle identifier. macOS version down to the hardware model. Steps to reproduce with real example links. Expected versus actual behavior. And one line that did most of the work for us:
> "The URLs themselves are valid, and macOS dispatches them correctly when they are handed to the system by any other means. The failure is specific to link activation inside MojoPad."
That sentence told us the bug wasn't in his links, wasn't in macOS, and wasn't in the other app — before we'd read a line of our own code. The report was right. MojoPad's link handler only let web links through; links meant for other apps were silently dropped. The fix shipped this evening as version 1.43.1, hours after the email arrived.
Who wrote the report
His AI assistant did. He told it what was wrong, and because it had access to his computer, it didn't just transcribe his complaint — it investigated. It reproduced the problem, tried the same links outside MojoPad and watched them work, read the app's version and bundle ID, and wrote the whole thing up with the evidence attached to each claim.
Two things struck us about this. First, the diagnosis was genuinely good — differential, specific, and honest about what it hadn't tested. Second, it made the fix nearly instant on our side: reproducing took two minutes because the report had already ruled out the wrong hypotheses.
Send us one like it
You don't need anything exotic — if you use an AI assistant that can see your computer, it can do everything the report above did. Paste this to it, tell it what went wrong, and email us what it writes: [email protected].
> Something isn't working in MojoPad and I'd like your help writing a solid bug report. Please: (1) ask me what went wrong, then reproduce it yourself if you have computer access; (2) check whether the same action works outside MojoPad, so the report can say where the failure lives; (3) write it up with a one-line summary, my MojoPad and macOS versions (MojoPad ▸ About MojoPad), steps to reproduce, expected vs. actual behavior, and anything you verified along the way.
No assistant? Use the same structure in a plain email and fill in the blanks yourself. Steps, expected, actual, and your versions — that alone puts your report in the top tier. And in the next MojoPad update, Help ▸ Report a Bug… will copy this prompt for you with the version lines already filled in.
There's a broader thought here we can't shake. MojoPad's last release was about letting you bring your own AI agent to your wiki. It turns out agent-friendly apps get agent-quality bug reports — the same tools that build wikis from a citation library will, when something breaks, tell us exactly where and why. We intend to keep earning users like that.