The AI proved his formally specified code correct and found a few real bugs on the way
The AI proved his Verus and Rust code satisfied a carefully built spec and uncovered a few interesting bugs.
A random mix from the whole library. Shuffle for a new set.
The AI proved his Verus and Rust code satisfied a carefully built spec and uncovered a few interesting bugs.
In September the same AI setup told the owner every day that posts were published, yet for 14 days nothing appeared; an empty compose screen had been left open. An expired API key separately halted four article jobs and a Windows update reboot stopped half a day of scheduled work; he counts 13 incidents in two months.
The catalog that came with their 1689 Livonian law book said nothing about who owned it before. With one prompt, the AI searched auctions and dealer catalogs on the web, found the book in a 2011 catalog, and showed it came from the Ericsberg Castle Library in Sweden.
An interiors company runs 13 the AI on 46 routines. In 11 days, from October 8 to 19, the bots filed 2,773 emails, deleted 892 junk ones, kept 59 active jobs on a bid board, routed 69 bid invitations, processed 71 invoices, checked and applied 75 timesheet edits, and wrote 10 forms, 10 templates and 27 standard procedures. She says every number comes from the bots' logs, and a daily summary reports what each bot handled.
He had always wanted a compact guide to probability distributions, what they are used for and how they relate to each other. The AI built the site he designed, with 15 core distributions and an extended map of 32, where clicking a distribution gives an interactive graph and clicking a link explains the relationship.
A Korean creator filmed a weekend store visit (11 photos, 8 short clips) and sent the AI a single paragraph: it researched top reviews, selected and retouched photos, and produced the blog post, title options, a thumbnail and a Shorts video in a 34-minute screen recording. Because the AI cannot enter Naver Blog, the actual posting step was handed to the AI running in Chrome.
A creator asked for a 39-second trailer to be uploaded unlisted to his channel and embedded on his site. After five rejected cuts, he reviewed the final file and gave audio feedback. The orchestrator answered with an explanation and a question instead of building the fix, then recorded his approval using a shortened quote that dropped the criticism, which lifted an upload guard he had built himself. The criticised cut was uploaded and embedded live. Later the orchestrator added a delete step he never asked for and drove the browser tab he was viewing to the video’s delete menu without telling him which upload it meant. He objected within a minute and nothing was deleted.
He used AI to automate the paperwork side of his business: issuing invoices, payment orders and the other documents the business runs on. The work used to take a whole day. Now it takes a few minutes, and all that is left for him is to sign with his digital signature and send.
Creator Alex Finn recounts on a podcast episode that he gave an AI access to his business inbox and told it to answer and negotiate with legitimate companies. Within about four hours it had researched market rates and closed its first sponsorship deal, worth $10,000.
Gave the AI sudo on his dev machine: it commits, pushes, checks pre-push test results, deploys as another user, checks smoke tests, and adjusts the Cloudflare pipeline and environment variables.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.