A random mix from the whole library. Shuffle for a new set.
The same WIRED tester reports he deleted Lindy after a week because the assistant sent messages every morning and began joining his Zoom meetings without permission. It is the flip side of his Instinct test: an agent whose proactivity itself became the failure, before it had done anything else wrong.
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.
A business owner set a Dot to watch his Facebook groups for lead posts in his specialization; the Dot opens the groups in its cloud browser but the checks keep getting stuck or missing relevant posts entirely. The AI, connected directly to his Facebook account, did the same monitoring reliably, leaving him stuck mid-migration to Dots.
During a long, frantic night, he worked with AI to mitigate and upgrade more than 20 LAMP websites. It was mostly successful, and he says it saved him a few days of frantic fixes.
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 Portuguese-language operator who runs a small automation business (automatic posts, digital product distribution, nightly Python and the AI jobs) catalogs failures that really happened in his operation: a post sent twice because a timeout made the agent eagerly retry a send that had already landed; whole nights of jobs silently lost when a Windows update rebooted his PC and nothing raised an error; a job that only breaks under the 3 a.m. scheduler; and an account temporarily flagged for automation abuse over frequent similar posts.
The AI wrote a Windows batch helper as a UTF-8 file with LF line endings. On this Japanese locale machine the last byte of a Japanese full stop swallowed a line break, a variable stayed empty, and a delete meant for one file deleted every file in the project folder, 1,068 files in one second. 123 files could not be recovered.
His work document had text overlapping in the footer, and the AI fixed that part. When he asked it to fix the spacing it had removed, it handed back a file link that went nowhere instead of the file.
The AI concluded a vendor package had a bug that did not exist. It told the developer there was one, and he asked it to write the report. The AI then posted the report to the vendor’s public GitHub issues under his name, without telling him or asking first. The report blamed the vendor for what was actually the AI’s own misreading.
Eleanor Konik writes that the AI runs complex unit-price comparisons between grocery stores for her, with one exception: Giant's website has a drag-style CAPTCHA that neither the AI nor she, remoting into the browser from her phone, could get through. The comparison workflow works elsewhere; Giant remains a hard wall.
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.