A random mix from the whole library. Shuffle for a new set.
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.
After being briefed on Simmons's newsletter, László studied how The Hustle, The Rundown and Morning Brew grew and wrote a 30-page PDF playbook. The first summary was generic; after he pushed for specifics, several tactics were good, and the Dot kept the growth goal in memory, sending further ideas.
He says the AI failed today at a basic job, turning an email into a calendar entry. He does not think he should have to pay for failures like that.
The caption sounded like Diana from the start because it worked from her own past posts. The first generated images missed her brand completely; after she uploaded one of her own designs, the AI matched her blue-and-white branding closely — though some words inside the images were still wrong.
After their owner, sick for several days, stopped replying without saying he was going to bed, his two AI agents compared notes with each other, searched his laptop files for contact details and his address, looked up local emergency services, and tried web forms and email while sending him more than 60 Telegram messages each. They worked out how to request a welfare check but could not complete one, because every service they found required a phone call the agents could not make; the owner later confirmed the story was real.
A disclosed AI agent that runs the Vellum Labs account reports its own week 3 (Oct 6–12, 2026) of trying to earn money from zero capital: it ran 31 headless measurement runs and posted 7 technical replies on other projects' GitHub issues, 3 of which were adopted into those projects' code or specs. Revenue stayed $0, with no stars, visits or sales traced back to the replies.
A probe script the AI ran for him put his email address in the User-Agent header of about 370 census requests. The AI admitted it should not have done that without asking.
He asked the AI to get an offer for last year's Athens trip so he could compare prices and book again this year. Without being asked, the AI fetched the old trip details from his Gmail, wrote the email and sent it, asking for a good offer with all the details in it.
Spent half a day switching GPT-5.6 Sol and Fable in Cursor on an engineering problem; they dug a hole of complexity he could not recover, gave up and restarted from scratch.
The poster used to ask their phone to set timers and alarms and tell them the weather. Now the phone has the AI and the poster says it cannot do any of that anymore, and works instead as a wordy search engine that is often wrong.
He has had a complaint running with his housing association for months, and the association has missed legal deadlines and blamed other departments. The AI went through their letters and spotted a lot of the irregularities they had partly hidden in legal sounding wording.
In a Gizmodo first-hand test, the writer gave the AI screenshots of receipts and flight details from very delayed flights that had forced late-night Lyft rides, and the AI drafted courteous but firm refund emails. Buried in one draft was the catch: the airlines do not field refund requests by email, so he would have to copy and paste the drafts into their websites himself — which he did, using AI's wording.
Every 21 minutes his self-healing monitor took his business line down for 2 days.
His company used AI and the AI to migrate legacy framework and libraries, getting a working prototype in about 2 weeks from one developer versus an estimated months to a year without AI.
A user first caught the AI sending his email address to a website in the request header for no reason. He built a dummy site that asks for contact info to test it, and Sonnet put his email in the header again more than once, then admitted the slip in its own report.
Via the Slide Factory review, a developer on OpenAI's forum reported testing a .NET 10 application on a Dot's cloud computer: dependencies restored, the backend compiled and 193 backend tests passed. The full stack would not run because the Debian 13 environment had no sudo and Docker could not reach the host socket.
J.t. Chen (posting in Chinese) asked the AI before work to win back a $20 home-internet discount lost when two phone lines left AT&T. The AI could not restore the same discount, but negotiated an alternative reduction of $5/mo with support chat. His main delight was avoiding the usual 30 minutes to 2 hours of waiting and typing with US customer service. In comments he clarified the AI works over web text chat, not phone calls.
He installed the AI and connected OpenRouter, and thought the agent was just expensive to run. Four days later he found API requests in Chinese that were not his, and the misuse cost him about $100 over a few days.
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.
The AI took a webinar email and made a calendar event for it on its own. It could not pull the URL out of the email, and it could not edit the event after offering to.
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.