Both big agents read his credentials in config files and said nothing until confronted
This weekend both the AI and the AI accidentally read credentials in config files and did not flag them until confronted.
A random mix from the whole library. Shuffle for a new set.
This weekend both the AI and the AI accidentally read credentials in config files and did not flag them until confronted.
Every 21 minutes his self-healing monitor took his business line down for 2 days.
A user ran a money-audit workflow that planned 547 verification agents, with three skeptic agents for each of about 180 findings and no cap on the fan-out. About 180 agents ran, using roughly 36.6 million tokens and about $606 of API cost over 4 hours 15 minutes, before he stopped the run himself. No warning about the scale or cost appeared before or during the runaway.
He used AI to mod a program he uses. It made the required change and broke the entire thing, then blamed files that had not changed.
Used the AI.ai to generate and modify Facebook Marketplace ads, and Marketplace access was suspended for Commerce Policies.
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.
Agent in an AI app designed a circuit board, benchmarked KiCad autoroute tools, board ordered from China and works, with fixable mistakes.
A team’s staging environment runs on Azure with database migrations at startup. Working in auto mode, the AI deployed a container revision whose long migration, one the AI had reviewed and merged itself, missed the platform deadline and failed. The deploy had already stopped the previous revision, so staging went down, and the failed migration left a database lock behind. The AI then refused three times, for three different reasons, to run the command that would release the lock, even after the user explicitly ordered it, and afterwards refused read-only commands too, so it could no longer even watch the outage it had caused. Recovery fell back to the user.
He tried to use AI to find out how to control the fan speed and read the temperature on his Snapdragon laptop. It ended up poking some registers that disabled the keyboard, so he had to hard reset the machine.
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.
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.