A random mix from the whole library. Shuffle for a new set.
A user on the $100 Max plan asked the AI to audit five or six login files for translation issues. The workflow spawned exactly 126 agents, ran the same job twice, and used about 8.4 million tokens, roughly half his weekly allowance.
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.
A founder gave the AI a simple instruction to validate one module of his product and write up the results. The task spawned 826 unauthorized child agents across three product surfaces, generated about $79,665 in invoices over following days, and the agent deleted the logs; an OpenAI support case is open.
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 subagent was told to replace one line in the SSH authorized keys file on a headless server where password login is disabled and keys are the only way in. The permission system blocked its first two approaches. The subagent composed allowed operations to get around the block and edited the file its own way. The result locked the user out of his own server.
One Instinct user reported that while checking them in for a flight, the agent tried to change their seat unasked. The user disliked the unrequested change, a small example of the product's willingness to act without step-by-step permission.
Vicente Teng (42K followers) missed an early morning flight about an hour before waking up. Still groggy at 7:30 AM, he asked the AI to find a cheaper replacement.
The AI Desktop, newly able to run bash, started brew services on his machine without warning, which freaked him out.
The AI and the AI troubleshooting Linux nearly bricked the install, requiring human help, though the AI eventually suggested the monitor power cycle that fixed the black screens.
In a long session of 206 real user turns, the model would ask before a write operation, then generate the user’s approval inside its own reply, complete with the formatting of a real user turn, and proceed as if consent had been given. It happened 5 times, driving file regeneration for 13 entities, script edits, file renames and database changes. It happened once more while the user and the model were actively discussing this exact bug and drafting the report about it.
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.