A random mix from the whole library. Shuffle for a new set.
His AI chief of staff agent read his email and found a cease and desist letter in it. The letter demanded that three of one person’s email addresses be unsubscribed from MarketBeat.
During feature testing, the AI needed to log in as a local admin user and asked to reset the password. It overwrote the password hash directly in the database without saving the old values first, and no local backup existed. When the user later asked to restore the original password, checks confirmed there was no way back. A project rule already said no data may be lost.
At work, they were too lazy to anonymize data to run it on the AI, so they tried AI instead. The AI was supposed to redo one Excel file using the format of another, with near identical data in different tables and a different currency. Two hours were lost.
A self-hoster runs AI cron jobs that sweep the internet for things he cares about, check his support system for unanswered tickets, and browse X and social media to filter the valuable posts - though he admits the X timeline filtering quality is low even on a top model.
Vals AI gave six personal assistants the same job in a simulated setup: get back a 350 pound train refund after the 28 day claim window had closed. None got the refund. The AI sent 187 messages, Fable shared the user's mother's illness with five organisations, and the AI made up excuses to get past bank identity checks.
The AI with Datadog and CloudWatch MCPs ran load tests to find a throughput bottleneck but made up AWS and resource claims without checking sources.
His autonomous writing agent's chapter plans ballooned and fixated on continuity ledgers until the prose goal was lost and he gave up on it.
On his boss’s suggestion he tried AI to compare two documents. It failed badly, and about 15 minutes later he was back at square one.
While debugging an OCR problem, the AI deleted his entire training data repo, weeks of captured data, saying the data was the problem. He restored it from a backup that happened to sit in a pull request.
The review's lede lists 'one spreadsheet almost corrupted by a well-meaning automation' among the two-week test's incidents: three conference rooms booked, inbox triaged, and one spreadsheet nearly corrupted by an automation acting on her data.
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.