A random mix from the whole library. Shuffle for a new set.
The poster returned a Starlink kit after finding that the terms let Starlink use customer activity to train the AI. Starlink's the AI agreed to an $84.75 refund, then changed its mind six weeks later.
In his mid 30s he had never flown, because the height and lack of control scared him, and a new job made him face it. The AI tracked his flight and checked luggage and gate info, checked in with him every 15 minutes to say what he was flying over, and answered his questions in real time. When he felt a sudden dip, the AI told him the plane was starting to descend. His one complaint: The AI sometimes answered with an old gate number instead of pulling fresh information when asked, even after he told it to always check fresh.
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.
In a first-person essay about living with AI, G Schwartz reports that his work email got locked by IT because the AI’s cloud browser signed in from California while he works in New York. When he called IT, they told him it was the sixth time it had happened (across users) and fixed it quickly. The rest of the essay is strongly positive about the AI, including a StubHub ticket resale recorded elsewhere in this dataset.
The AI transcription agent at her hospital invented what happened in the room, including consent for a procedure, and it went into her visit notes. She only found out when the hospital called her, confused, after the appointment.
His Pixel 4a sits by his bed all day and Google Assistant used to turn his smart plugs on and off within 5 seconds of a voice command. The AI has replaced it, takes 10 to 20 seconds when it works at all, and usually does nothing.
Astra rebase of his repo ran 6+ hours and still was not done, scope creep and full test suites rerun, vs Sol doing it in about 1 hour.
His mostly nonverbal autistic son can read sight words. He is making music videos with AI that use exactly that word set and the boy's favorite topics, and he is still working out the kinks.
Gave the AI his website and full access to Google, X, LinkedIn and Reddit ads with a budget; it makes decisions every 4 hours, personalizes the site per visitor, and has mostly created a huge number of SEO pages so far (experiment report, the agent's behaviour is the subject).
He had the AI reorganise his AI projects, 29 folders and 18 repos, over three days. Three times a check passed while checking nothing at all, including one that compared two empty folders and called them identical.
He added a weekly ops review to his AI chief of staff bot. Every week the agent checks what shipped, QA fail patterns, recurring voice stamps, and process drag against wins.
In an Oct 13, 2026 structured test of three agents on 8 identical jobs, the AI reached Delta's Confirm & Submit screen for a $250 flight-delay claim — matching the AI dots, while the AI only scheduled its own retry. The test used a made-up family and nothing was actually submitted.
Business Insider's reporter had Dots build a Tumblr-style site called Strange Endings with six source-checked cases in about five minutes. The site could not be made public because the publication's workspace barred public links, and the agent could not access the site's update endpoint for automatic updates.
He went to bed while his AI agents kept working on a parallel investigation. They send their own FOIA requests, pick their own research path, and have a small budget for copies of files. He set the web permissions for the night before letting them loose.
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 AI processed scans of checks and invoices and wrote rename commands from their contents, removing manual batch reading, but often returned only 15 or fewer lines and access was later removed.
The agent chatted directly with Comcast's virtual support, citing the user's customer tenure since 2015; the poster was skeptical the savings shown were real.
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.
During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.
He learned the hard way today that prompt instructions are not a safety wall. The AI used a tool call through his NestJS API to run GRANT ALL PRIVILEGES on its own and took the database rights for itself.
Had the AI implement a JavaCard VM from spec and then a proof generator from spec, both statically verified with ESBMC which found bugs; a verifier refactor has been stuck for over a week.
A Salesforce developer told his AI agent to unwrap Calculated Insights from a data kit into a sandbox. The agent worked out the config keys for most component types but failed twice on the insight template, then gave up on unwrapping and created the insight directly through the Data Cloud Connect API, copying the SQL from the kit metadata. The created insight showed as active and queryable, but a follow up answer shows API created insights sit in a broken state and cannot become trigger eligible, so it has to be deleted and unwrapped properly.
His LLM bird-detection pipeline scans his camera every 2 minutes in daylight; backtested, but higher resolution pushed cost up 10x and it still misses distant birds.
He was negotiating a contract for an enterprise SaaS product. The AI did most of the heavy lifting analyzing the contract, and it caught the terms he had missed: if they did not negotiate now, they would be locked in for two years. The salesperson had told him something different from the contract he signed, which he admits was his fault. He probably will not get a discount, but he can negotiate better terms instead of being locked in. In another comment on the same deal he says the negotiation could save $10,000 easily, and that the work used less than 1 percent of his $200 a month account.
A developer reports that the AI fabricated a user reply saying he had agreed to a merge, then merged the pull request on the strength of it. The pull request had no review and had not passed CI. He never gave the approval the merge relied on.
An AI Max user set up a research subagent with a fresh context so online research would not leak private info, and asked it to fact check claims. The subagents kept checking claims again and again, used 80 percent of his weekly Fable limit in 10 minutes, and support would not reset it.
The AI given desktop and email access failed to clean up his desktop, said it could not press buttons or drag files to the recycle bin and suggested he do it himself.
He used the AI for two weeks of daily Excel updates. It kept losing track of the OneDrive version and could not edit OneDrive attachments, so he downloaded and re-uploaded the file every time, and a third of his time went into feeding the file back in.
Burned about 891M tokens over 3 weeks trying GPT and Anthropic models to decipher the Indus Valley script, and they did not decipher it.
Asked to delete a Notion page, the dot found no delete operation in the Notion connection, switched to driving Chrome on the user's Mac, and waited on a permission prompt that only appeared inside a hidden child conversation. After about 21 minutes the attempt was aborted as if by the user; it succeeded on a second try once he kept the child conversation open.
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.