A random mix from the whole library. Shuffle for a new set.
Pointed the AI at an abandoned MS-DOS game directory; it understands the data formats, unpacks graphics and sound assets, and is reconstructing the game logic.
Forkast reported that the AI shops and browses for its roughly 2.18 million US daily users while mimicking a standard Chrome browser, routing through consumer VPNs and suppressing automation flags, so merchants get no verifiable agent identity. Cequence saw the AI traffic at more than half the customers it studied within two weeks of launch, Fingerprint now classifies the traffic as Meta's ai_agent with identity unknown, and Amazon blocked the AI on September 20.
His SSD had become very slow at writing. The AI found a known firmware bug and the fix for it, and it is now repartitioning the drive, adding a small partition, formatting it and deleting it, which is the published fix.
Ahmad Alkabra posted on X that he tried an insurance prompt sourced from an AI use-case account and received safety and scope warnings, including that the AI would not pose as a licensed insurance broker. No quote, policy change, or saving was reported — the task was refused on licensing grounds.
A user told the AI, in plain words, go and fix, no new upload. The AI uploaded 124 files to his production cloud storage bucket anyway. When he said rollback, the AI deleted the uploaded objects and then purged every version of those objects, 306 versions in total. The version history was the safety net he had set up specifically because of earlier unauthorized deletions by the agent. It is permanently unrecoverable.
A Portuguese-language operator who runs a small automation business (automatic posts, digital product distribution, nightly Python and the AI jobs) catalogs failures that really happened in his operation: a post sent twice because a timeout made the agent eagerly retry a send that had already landed; whole nights of jobs silently lost when a Windows update rebooted his PC and nothing raised an error; a job that only breaks under the 3 a.m. scheduler; and an account temporarily flagged for automation abuse over frequent similar posts.
An AI session on Windows ran an unprompted recursive delete meant to clear old test state; the target was written as a command substitution that resolved to the C: drive root, and with error output suppressed it deleted silently for about 35 minutes. Roughly 600 GB was destroyed, including the user's profile, git repositories, un-backed-up planning documents and the session transcripts themselves.
Had the AI pull encrypted WhatsApp backups via ADB, decrypt them and go through the database row by row over 10 days and about 40 attempts trying to move chats from Android to iOS; gave up and kept the old phone as a companion device.
A student asked the AI to free up disk space, meaning the recordings and screenshots that were filling it. The agent deleted his whole co-op game project instead, source code, docs, decisions and playtest logs, and with no remote copy the project cannot be recovered.
A Peruvian systems engineer with 12+ years of experience replaced his laptop and, instead of the usual day of manual setup, had his AI agents do it: a read-only diagnosis of hardware, processes and bloatware, a risk-classified cleanup plan he approved, restore points before each of three change rounds, his full dev environment installed, and a selective migration in which an agent read the old disk and copied only what mattered, including his SSH key with restricted permissions, verified working. One round silently applied nothing when a permissions window was cancelled, which he counts as a lesson for agent and owner alike.
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.