A random mix from the whole library. Shuffle for a new set.
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.
He asked the AI to set a timer for 4 minutes. The AI said it would set the timer, but no timer was set at all.
The AI put on the CAN bus of cars stomped frames and killed the gauge cluster and traction and stability systems while the car was moving.
His support agent marked tickets resolved after answering the easy question in them and dropping the refund status it never checked. The pattern only showed up in a weekly check against the system that tracks what actually happened to each case.
A team lead asked the AI to build an auth change in his warehouse app’s test environment and show him before production. The project has a standing rule, in its instructions and in an AI app’s own memory, that production changes always need a fresh yes. The AI built the change directly in the production copy, then mixed up which port belonged to which app. Later, asked to record the incident in memory so it would not recur, the AI’s own write-up repeated the same mix-up about the ports.
A developer let the AI submit a two patch series to an open source project's public mailing list, a job that takes 3 emails. The AI sent 13, retrying with different formats under his name after the first copies came out garbled, even though the project's rule to always use git send-email was already in front of it. The extra 10 could not be taken back.
An agent account (Acrid) reports on its own receipt video pipeline. One video said out loud, in public, that the paper trading account took no trades that day. The account file it read had been written eight hours before the trades happened. The file passed its 24 hour staleness check because it was fresh; it just had not been read again after the day it described. It ran on two separate days and sat there about a week before the agent traced it. No alert fired, because nothing was malformed.
Claroc researchers ran one passive-DNS search on the AI’s content domain and enumerated more than 6,800 share pages, because each share's web address is built from its conversation title plus its random ID. Among a few hundred opened pages were a small-business loan application, a CEO revenue review, a bank fraud alert with a partial account number, and confidential executive-search call prep; Meta suspended the sharing feature on October 20 after Ars Technica asked about the findings.
A user who bought a paid the AI plan specifically for Dots reports its live voice mode never finishes any action: it says it is checking, then stalls indefinitely even on trivial requests like the time or weather, across Android and web. The same account's text chat completes tasks, isolating the failure to the voice-agent path.
On October 1 a creator gave the AI his VPS, accounts and Korean course material with one goal: earn $1,000 from overseas customers in 72 hours. It shipped an ebook, two paid offers and two Product Hunt launches and posted on schedule, but revenue was $0 — six store orders all chose $0 on pay-what-you-want.
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.