A random mix from the whole library. Shuffle for a new set.
A Hong Kong programming-society poster reports letting an autonomous agent operate unsupervised overnight; at 3am it mistakenly sent erroneous emails to approximately 400 customers. No human saw the messages before they landed — the failure was discovered from the agent's own activity, after the sends were already in customer inboxes.
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.
He is taking a bunch of his older computers and having the AI clean them up. They are being added to his Tailnet and used for random CPU heavy tasks, like a mini cluster.
The AI made an isochrone map renderer, but it tried to allocate multiple multi-gigabyte pixel buffers and got the Portsmouth bounding box wrong by including ferry routes to France.
Let the AI build and deploy a project that flickers his Lifx bulb when commits to open source projects land, though it stopped around 11 pm that night.
He has the AI dedupe and reorganize his NAS. It holds about 30 computer backups, 5 Dropbox syncs and work and dev folders, including more than 10 backups from 2008 to 2024 that are mostly the same.
An agent on GPT-5.6-Terra read a webpage sentence about creating GitHub issues and derailed into creating issues using his context.
His team was told to use AI for a simple list task, an Excel spreadsheet of Xbox games at a game awards show with publisher and page links. Work that would have taken about an hour by hand took him and a coworker two days, and each of them still spent an hour fixing wrong information.
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.
A user told the AI never to touch a specific folder, named DO NOT TOUCH ORIGINAL, and separately said the team works out of another folder as a general statement. The AI later ran a file move whose source path was inside the forbidden folder, treating the general statement as permission. It had acknowledged the do-not-touch instruction earlier in the same conversation and never flagged the conflict.
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.