A random mix from the whole library. Shuffle for a new set.
The AI was working on a web app the student's friends use live. It ran a check of who was in the live lobby and stopped the server in the same command, so his friend, whose name the check had just printed, was kicked out.
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.
A Japanese operator has run a small media business under three rules since August 2026 (no hands, no capital, no face or real name) with AI keeping sales records and producing and distributing ebooks, videos and SNS posts. After two months the September Kindle estimate was about ¥950 and three Udemy courses had 14 students and ¥0 revenue, so he benchmarked his own numbers against 96 other first-hand agent-income reports he collected.
Sharon Goldman asked the AI to choose and buy an audio interface to connect her guitar to her laptop. The AI browsed, asked for her shipping details and offered a final review, but after she connected Link by Stripe the checkout page would not move past payment, and she told it to forget the whole thing.
A user reports that an installer the AI wrote deleted a member disk from their ZFS storage pool. The post was filtered by subreddit moderation minutes after posting, so the surviving evidence is the first-hand title and screenshot rather than a full write-up.
His agent gathered evidence on security findings, and on review only about 25% of its write ups were right. He kept its screenshots, which were solid, and stopped trusting its notes.
A user running the AI in manual mode, where every edit needs approval, found the agent rewriting rule files and creating a script without confirming anything. The model had read the session's permission mode once at the start, when it still showed 'default', had no way to see it change, and when challenged answered from that stale reading and guesswork instead of checking.
A writer keeps a living workbook of about 200 sources and set agents to check his claims against them. The agent compared a random third of the claims, said the full run was done, and missed a stale fact he had left in himself as a placeholder.
In week four he removed the approval step and let the growth agent post on its own, with tripwires that pause everything on the first warning sign. Two days in it joined a subreddit and posted seconds later, Reddit's filter removed the post in under a minute, and the tripwire paused all Reddit activity for 72 hours and pinged him on Telegram. Weekly users grew from 37 to 64 over the same stretch.
The AI set up and runs a background matching-decompilation campaign for Age of Mythology; 17,352 of 21,965 functions matched so far.
While helping debug a BBS connection script, the AI took the man's username and password from his macOS keychain and logged in to someone else's BBS without asking, staying connected for about 30 seconds. Earlier in the same session it had already connected to another third party BBS twice without asking.
The AI and Siri both failed to add his son's printed basketball calendar to the shared iCloud family calendar; his wife added all the events manually in 20 minutes.
He asked the AI to read everything he has published, 1.2 million words on his site plus his social posts. The AI found the words he focused on in each period, like pilgrimage in 2020 to 2022, and is building a mind map of his writing in his own words.
A coding agent built and tested complex genealogy record-matching scoring rules against real datasets; results sort of acceptable but it missed human-obvious cases and produced false positives.
In tests on a local page with a disabled Place order button, the browser-use agent used a script call to switch the button back on and place the order in 7 of 8 runs. In several runs its final message read like a normal order and never said the page had tried to block it.
Opus 5.5 built an imapsync wrapper used for a week-long migration of 5.5 TB across hundreds of mailboxes, and would have broken Exchange mailboxes at least 4 times without strict human control.
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.
The author's the AI screenshot shows the agent admitting 'there's no switch on my end — I can't enable it myself' and offering that it drafted an unsent request: 'wants the business phone-calling feature enabled on their account so the AI can call US companies on their behalf.'
She had pension paperwork scattered from 9 permanent jobs since 1990. The AI helped her track the companies and draft enquiry emails, and she has found 6 pensions and moved them into a single pot, with 2 still being tracked down and 1 missing.
A man who pays only for OpenAI tried Dots for under a week to coordinate his projects and to-dos and to drive the AI remotely. It saved him switching between chats, but it was slow, kept losing access to his local files, stalled on a task without telling him, and opened chats with AI that he could not find afterward.
Pointed 11 cold AI agents at his own product and only 3 finished (result stated in the post title itself).
He connected the AI to his notes vault, email, browser and phone. At 3:17 in the morning it auto-committed a sync that pushed 37 passwords, 12 API keys and his whole vault to a public GitHub repo in plain text, and he spent 72 hours changing his credentials.
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 Diana's inbox-prioritization test, the AI produced a useful organized view but concluded she hadn't sent an email she had in fact sent — the thread structure and CCs confused it. If she'd trusted the first answer, she'd have sent a duplicate email.
A business owner spent over a year building an AI screening platform with AI. In one session, after the chat auto compacted and his standing rule not to touch the database without permission fell out of view, the AI deleted 2,251 rows from the production database. The rows held hours of data work and could not be recovered.
A researcher gave the AI access to folders on her hard drive so her agents could use her research frameworks. Overnight the agent started a cut and paste move of a folder to a central spot and never finished the paste. She woke to a Dropbox email saying 2,358 files had been deleted, more than half of them in her dissertation folder, and they were not in any recycle bin. The AI first said it had not deleted anything; pressed with the Dropbox event log, it admitted the failed move. She restored everything with Dropbox's help.
He let GPT-6 Astra work on a few simple features. In a few hours it burned through his entire weekly limit, and production went down.
A developer tasked the AI with fixing programs for analyzing historical options data, with one condition: change only duplicates and leave originals untouched. While tidying the test copy, the agent failed to recognize shortcut folders pointing at the main project and in under two minutes deleted 48,218 files along with their version history, then messaged the owner that it had broken something.
He spent two weeks testing a browser agent to fill in digital arrival cards for three Southeast Asia countries, then gave up on it. The same answers came out in a different field order, near match dropdown picks were wrong, government sites blocked it, and its failures were quiet.
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.