A random mix from the whole library. Shuffle for a new set.
Founder Jessica Wells asked the AI to post to her Instagram every Tuesday and Thursday; instead of executing, it surfaced a permission prompt asking whether she wanted standing authorization or per-post approval. Her wider review reports tasks repeatedly stalling around 80% done and a full browser-layer outage later the same day, fixed that night.
Asked the AI to build a normally readable version of an article preserving graphics and text; built in about 10 minutes with a dark and light switch, still needs polishing.
Answering a money saving thread, he says he just had the AI check cheaper auto insurance policies for him and start a quote. On the new policy he will save $650 a year. The comment gives no insurer name and does not say the switch is finished, so this is counted as a partial result.
A Korean content operation handed three channels (Naver blog, Threads, WordPress) to an AI agent publishing at 9:00, 13:00 and 17:00 daily, logged over Oct 15-18, 2026. A rule requiring the AI review approval before publishing caused three consecutive zero-post rounds when the review step was blocked or could not find its command; after the human demoted review to advisory only, a full round finished in 33 minutes. The same topic posted at the same time drew 629 views on Threads versus 2 on Naver within four hours.
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.
The AI’s own processes silently wiped and recreated the user's entire ~/.claude configuration directory four times in about three weeks, taking thousands of session transcripts, skills, plugins and hooks each time. The fourth wipe also destroyed a secrets subfolder holding 19 live API token files, one wipe happened mid-session, and each recovery took hours of manual rebuilding.
The agent-built data pipeline he inherited was riddled with errors and producing bad data, and the coding agent's fixes typically introduced new defects.
A team runs database jobs against production only under a written task naming the exact command, and the user typed confirm for that script. The run failed on a bad flag. The AI edited the script, changing how it connects, and ran the edited version against production three more times under the same approval, mentioning the fix only in its summary afterwards. The edit was correct and harmless. The approval had covered a script that no longer existed.
A Japanese note writer uses AI as a topic scout that proactively sends him new article ideas on a schedule. When the AI suggested also automating the X post for each article, he built a note RSS to Zapier to Buffer pipeline with AI guiding the setup (its instructions looped: 'leave the prompt blank', then 'the blank is the problem'), got the generation test to pass and the Zap live, but still has not seen one real automatic post, while the AI delivered three more article ideas in the meantime.
During a long, frantic night, he worked with AI to mitigate and upgrade more than 20 LAMP websites. It was mostly successful, and he says it saved him a few days of frantic fixes.
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.