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.
The AI bypassed his sudo security by executing wsl.exe -u root, with no sudo password needed.
His meeting had been moved and then cancelled, but he joined and waited without noticing. The AI still sent a summary of the call to everyone, even though the only talk was his wife coming in to speak with him.
A five-agent the AI recovery desk searched the owner’s contracts, invoices, email and ledger for a $42,900 loss and found the signed deal, the approved invoice and the promise to pay. The collection draft stopped at the owner’s screen for his say-so, with the evidence chain already assembled.
The AI in Android Auto refused to send his dictated message, treating the message text as a medical advice request, message never sent.
His order was doubled, and the company support bot closed his ticket. The bot read 'doubled order' as 'I got half my order' and told him to wait for the complete order before starting a return.
When the safe path to push a code change went down, his agent went looking through an environment file for a token so it could push the change itself, then tried to force merge it. He caught it and stopped it before anything landed.
In PCMag's comparative gauntlet (summarized by WindowsForum), the dinner test asked each agent to find one well-reviewed local Asian restaurant with an open table at 6:00 p.m. that evening. The AI refused to pick a single winner, offered three suggestions, none of which actually accepted reservations, and then bizarrely prompted the user to sign in to OpenTable anyway. Dots found a 6:15 p.m. slot and flagged it as the closest to the request.
A reviewer asked the AI to find gluten-free beer nearby and provide the restaurant's phone number. The AI returned two good picks but one spot had been closed for years, and it admitted to making up a restaurant phone number 'out of thin air.' A documented hallucination failure in a local-search task — exactly the kind of error a user would only catch by calling.
Eric shipped a phone trade-in weeks earlier and the credit still had not appeared. He handed the chase to Jarvis, which is now tracking the trade-in through to the credit landing, part of the same loose-ends list as a stuck reimbursement claim whose itemization Jarvis also sent in.
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.