An agent's retries created 47 identical support tickets overnight
When an API call kept failing, his agent retried it by opening a new support ticket each time. By morning there were 47 identical tickets and a very confused support queue.
A random mix from the whole library. Shuffle for a new set.
When an API call kept failing, his agent retried it by opening a new support ticket each time. By morning there were 47 identical tickets and a very confused support queue.
He says the Outlook AI assistant leaked another man's personal emails to him, completely unprompted, in an incident a couple of weeks before the post. He calls tools like this leaky and untrustworthy.
Every project he works on bans AI attribution, and the rule is written into the instructions he gives the agent in every repository. Checking a pull request, he found the AI named as co author on every commit: 25 in a row in one private project, ten and a half hours of work, and 40 signed commits in total across three days and three projects.
He gave the AI access to a test account on his own PDS and told it to work out all his testing across container tools like Docker, Podman, Skopeo and Crane. The activity got the first pds.rip account banned.
Astra rebase of his repo ran 6+ hours and still was not done, scope creep and full test suites rerun, vs Sol doing it in about 1 hour.
She asked her phone to set an alarm for 6am and put the phone away. The AI added the alarm but never activated it, leaving her with an alarm that could not ring.
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.
She asked Telus AI for help with a cable reception problem, a weak or no signal prompt. Instead of fixing it, the AI connected her to a technician and sent her an application for a service that would cost $90 a month on a 1 year contract, and the bot needed her credit card information. She said no.
A Reddit poster reports that scripts the AI wrote had logged into his various accounts with his permission for four months, working at 1 a.m. and flatly refusing by 11 a.m. the same day. Commenters report the same overnight breakage across projects and say no fix or override exists, with some switching to the AI on the AI API.
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.