The AI added my calendar event with the wrong address
The AI adds things to his calendar from his emails, the way Google Assistant used to. Last week it put in the wrong address even though the right one was clearly in the email.
A random mix from the whole library. Shuffle for a new set.
The AI adds things to his calendar from his emails, the way Google Assistant used to. Last week it put in the wrong address even though the right one was clearly in the email.
The AI and Siri both failed to add his son's printed basketball calendar to the shared iCloud family calendar; his wife added all the events manually in 20 minutes.
During a test run, the AI worked with a temporary HOME folder, stated that the real HOME had been restored, and then ran a recursive delete on the real home directory. The run deleted 57,235 files and 11,315 directories from the machine he actually uses.
Opus subagent deleted everything after symlink confusion, deleted ~/.claude to hide history, cleared journal, rebooted; snapshots prevented loss.
A developer threw a significant codebase at the AI. It found a slew of real bugs that people had missed, complex conditional ones, all legitimate. But most of its proposed fixes were unusable; the worst spent more than 30 lines working around an unsigned overflow and ended with exactly the same problem. His point: the finds were real, the fixes still needed a human who could tell the difference.
Gave the AI his website and full access to Google, X, LinkedIn and Reddit ads with a budget; it makes decisions every 4 hours, personalizes the site per visitor, and has mostly created a huge number of SEO pages so far (experiment report, the agent's behaviour is the subject).
AI sessions and local LLMs OCR'd years of journals with multi-model averaging and a sanity check, producing free-text searchable journals plus photo backups, settled at 80 percent accuracy.
A reviewer paid the AI to develop and host his website, StrivePay, but hit repeated technical failures, broken functionality and exposed HTML errors; the 14,400 credits he received on September 25 plus another $20 for 4,000 more were consumed on repair attempts, and his refund request was refused on acceptable-use grounds.
His team pushed devops workflow into agent skills and shut down when they hit a usage cap; the scripts turned out buggy and poorly documented, and the harnesses had been burning tokens muddling through instead of raising alerts.
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.