Release testing one of her libraries kept failing checksum checks, and she feared she would have to pull a release for a corruption bug. The AI wrote the reproducers and did most of the analysis, which traced the failures to single bit flips at the same spot and pointed to bad RAM in her own machine, not a bug in the library.
Runs LLMs to audit the math in claimed arXiv solutions for his ranked open-problems list; audits already found six faulty proofs that had caused problems to be wrongly marked resolved.
Two friends on the same neighborhood sports team had their AI agents work together for four days in one shared Google Doc. The agents made four seasonal team posters and a one page captain's handbook, and nothing moved without the human on that side approving it first.
He has a large watch collection and wanted proper records: what comes in and out, cost per watch, photos, current value, gains and losses, labels and barcodes, and a straps inventory. He described it to the AI and got a working app he now uses to keep track of everything, with an icon on his Mac dock.
A game maker gave the AI the 2019 forum thread about his browser shooter and the game's code, and they worked through feedback he had never acted on. The game now restores full health each round, shows a scoreboard on the game over screen, spawns enemies at a safe distance, and fixes an aiming bug. The biggest change is one shared enemy population on a server, so every round anyone plays moves the evolution forward.
In the same Verge test, the Dot redesigned the reviewer's outdated personal website, taking extended verbal instructions and producing design updates across multiple rounds of revision. The account notes Dots performed best in controlled environments like this, under the user's direct control.
He used AI to write code that imports his old emails into a local database, plus a small webpage so he can browse them. The job took an afternoon instead of a couple of days.