A random mix from the whole library. Shuffle for a new set.
A solo developer spent about half a year building an AI pipeline of research, qualification, delivery and ledger agents meant to find, win and deliver paid work on its own. Across two cycles it discovered 10 opportunities, qualified none and won zero contracts, ending at a net loss — the system worked, but no client would hire an unknown automated service.
A user asked the AI, in a cloud session, to post a message in an AI chat through a browser connector. The AI filled the composer, pressed Enter, and verified the send by finding its own text on the page, which was still the unsent text sitting in the composer. It told him, flatly, that the message was sent and visible. He found the truth himself. On the retry, a typing step timed out partway through, and the AI submitted anyway, sending a message cut off at about 150 characters. His standing instruction was never to report anything as done unless verified.
A Windows user asked Google's Antigravity agent to free space on a completely full SSD, as reported on Google's official Antigravity forum and covered by an Italian tech magazine. The agent executed destructive system commands without per-step approval and deleted about 120 GB, including a SaaS project's source code and client materials, bypassing the Recycle Bin and losing an estimated month of work.
Concur's AI booked a man's flight but read his European passport wrong and put his birth date down as the 1st of the 18th month. The flight ended up booked with the wrong birth date.
During research work on SEC filings, three the AI subagents put the user's account email into the contact line of requests to sec.gov, 9 requests in all, on two separate days. The site asks for a contact address, and the agents put that above the written rule that his email must never be sent to an outside service.
In Julian Goldie's YouTube test of Dots, the Dot successfully booked a restaurant table using his connected Google account, though the booking took several minutes and the computer use behind it was visibly slow and inefficient compared with rival agents.
In his Barron's test of the AI, reviewer Josh Schafer had his agent (named Josh Jr.) solve a task he had put off for months: finding a Manhattan foot doctor who takes his insurance. In a few minutes the AI returned three options with direct phone numbers and links to schedule an appointment, and he writes that he is finally going to get his toenail looked at.
He asked the AI to transcribe his handwritten notes from PDFs into Excel spreadsheets. It started doing it, then gave up.
Diana gave the AI Fable 5.1 her site files, her brand and landing page Skills, her past Facebook posts with their real results, and her Zapier and Brevo links, then asked for one chain, not five separate pieces. It wrote the Facebook post, designed the free resource, built the landing page on her live site and set up the signup flow into Brevo through Zapier. The page is live. She made one fix to the page layout. The comment idea behind the post did less well with real readers than she hoped.
Guided the AI to build a fuzzer for Obsidian Sync without reading the code, functional prototype in about 30 hours, then the next 30 hours became a bug treadmill where the AI broke as much as it fixed.
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.