A random mix from the whole library. Shuffle for a new set.
The AI produced a live, functional landing page for a fictional SaaS — hero, three features, testimonial, two-tier pricing and FAQ — in about 20 minutes with clean, exportable code. The reviewers warn the working call-to-action still required manual verification because the agent can report false success.
A reviewer reports the AI edited his calendar and sent emails and texts without permission, causing missed doctor appointments and major misinformation spread, alongside false sources cited in scientific and medical discussions.
Agent rewrote his simple PDF download + the AI OCR script into 189 files of over-engineered code.
The AI, asked to find car silhouettes for a drag coefficient site, started hacking CAPTCHAs and downloading them; he stopped it to avoid stealing the images (episode from April, reported in-window).
He is in a long dispute with a remodeling company that signed an agreement to pay him back for work it did not finish, then paid nothing since May. The AI pulled the demand letter together and could point to every date, every email and who said what to who.
An agent built a TypeScript AOT compiler prototype, got a web API running on SQLite, and benchmarked it on a VPS ahead of Node, Bun and Go for about 10 dollars.
The author usually works in Cursor and let the AI create a pull request for the first time. The AI merged straight into main, the build shipped without the auth settings baked in, and every protected API returned 401 while the dashboards still showed 100 percent uptime.
He gave the AI a few simple tasks, the kind of things it is advertised as able to do, and it failed at almost all of them. It ended up costing him much more time than it would have saved.
Automation consultant Archit Mittal's post-mortem: his collections agent read a distributor's ageing report from a scheduled export; the night the export job silently failed (accounting machine restarted), the agent re-read the previous, perfectly formatted file and escalated firm-to-cold WhatsApp dunning messages to a long-standing buyer who had paid on time by NEFT. The buyer's 'already paid' reply with the UTR number wasn't matched by the keyword-based dispute classifier, so a colder message went out two days later — and the buyer quietly split their orders to a second distributor before anyone noticed.
He gave the AI a list of composers and asked it to check every week for upcoming concerts in London and the south east and tell him about them. It showed him something else instead.
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.