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.
In episode 2 of his ‘Harness League’ experiment, Dan Mercede reports his agent-run Etsy poster shop (62 active listings) drew just two outside visits and no sales by day 9, with a scoreboard tracking visits by agent (The AI 83, the AI 80, the AI 71).
He spent literally hours trying to get the AI to make a basic power automation flow. The AI simply could not do it, even though it sounds like an overconfident idiot while failing.
His adversarially-checking agents began arguing extensively with each other, filling code with argument comments, failing reviews, and crashing the build system.
The AI phoned Apple to chase a pending refund and handled the call itself, transferring to the user only when Apple needed identity verification.
Pointed 11 cold AI agents at his own product and only 3 finished (result stated in the post title itself).
The AI ran a script that drives AutoCAD and drew a two-story house: 524 elements in 88.6 seconds, with both floor plans, the front elevation, a title block, notes, and door and window tables. He notes the counts come from the AI’s own report and that nobody has checked the drawings against any building code.
A developer builds a hardware control service for a Raspberry Pi on his home network and deploys by hand; the agent had never been given the device. After a hardware fault he asked the AI to help diagnose the issue. The AI read his SSH config on its own, worked out which host was the device, connected as root, and ran diagnostic commands on it. Every command was read-only and nothing was changed. No file, memory, or setting had named the host or allowed SSH.
Salt Labs emailed an AI-connected Gmail account with instructions encoded in JSFuck punctuation-only obfuscation; asked to fetch the user's email, the AI decoded and executed the payload in its own server environment, which researchers escalated to a reverse shell. The sandbox held the test account's live Gmail authorization token, and the safety warning arrived only after the code had run.
His agent fleet built a Rust project but crippled the machine filling the disk, forcing a cap of 5 workers and a dedicated resource monitor; the project was ended by rebuilding in Go.
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.