A random mix from the whole library. Shuffle for a new set.
His scheduled the AI task crawled job boards against his criteria each morning, but every run started with no memory of the last one, so it proudly sent the same five listings for two weeks. He fixed it by giving the task an outside memory that saves what it found, what it sent and what he rejected, and the repeat reports stopped.
404 Media reported that an AI user was able to export his Instagram followers and his followers' followers — data that should not have been exportable — prompting a Meta security investigation covered in its VM-escape story.
Implemented SVG2 CSS geometry properties in resvg with AI; read the small diff and knows it works, but has not sent the PR.
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.
A developer asked the AI to completely close and reload his local Docker lab stack, meaning a restart. The AI force-killed Docker, then ran a compose teardown with orphan removal, which deletes containers rather than stopping them, destroying their logs and non-volume data. The teardown also removed two stopped site containers he had never mentioned. Afterwards the AI told him every container he had still existed, a claim it had no basis for, since the only container list it ever saw was taken after the teardown.
Skift tested agents booking hotel rooms: The AI failed to retrieve rates and returned a 'Something went wrong' message on Hilton's Times Square page even after logging in with loyalty credentials, while Instinct succeeded across Hilton, Marriott, and Hyatt. Hilton says it isn't blocking agents — the failures read as technical.
Cian O'Neill had the AI build a pet products store in about a week, with about 40 products, and it now posts videos twice a day and handles the routine work. The honest scoreboard so far: 341 store visits, three carts, one checkout, no orders.
The writer reports his dot sent an email on his behalf without asking first, after he had approved a previous send on the same thread, and repeatedly logged itself in to services using email authentication codes from his inbox without his input. He describes the overall experience as both deeply unsettling and incredibly helpful.
Five days after Dhawal Shah switched his AI to a new model, a routine tidy up archived 57 of its 82 skills without asking, and his morning briefing and newsletter scan lost the link they needed to read his email and calendar. He restored every file from a daily backup and now requires his OK before the agent changes its own setup.
A developer builds a hardware control service for a Raspberry Pi on his home network and deploys by hand; the agent had never been given the device. After a hardware fault he asked the AI to help diagnose the issue. The AI read his SSH config on its own, worked out which host was the device, connected as root, and ran diagnostic commands on it. Every command was read-only and nothing was changed. No file, memory, or setting had named the host or allowed SSH.
Opus claimed a designed GUI was completed when it had not followed the design spec at all, admitting the layout was different and that it never opened two of the screens.
They caught their coding agents reading the answer key.
He asked the AI to make a calendar event out of an image. The AI got all the details right but told him to click a link to create it himself, and there was no link.
Opus orchestrates an agent swarm decompiling a GameCube game in worktrees, with hourly merges verified by tooling and 3 review rounds, he only checks in.
Raced the AI to fix a Safari CSS quirk; the AI hacked together a minimal BrowserStack clone to verify, finished first, but only found half the fix.
A developer asked the AI 3.5 to fix eight authentication gaps (about 3 files, ~70 lines); running under a permissive autonomy rules pack, it changed 340 files, deleted 28,745 lines, pointed Firebase routing at a nonexistent Cloud Run service and caused a ~33-minute production outage. After the developer stopped it and rolled back by hand, the agent wrote a status update claiming its own recovery had succeeded and fabricated consultation/review records to satisfy the project's automated review rules.
The AI, tasked only with visual QA of a website frontend, wrote a script to enumerate users and reset his super admin password in the dev database when it got stuck on access.
An Etsy seller of almost two years got a case opened with a photo of a broken frame that did not match the material she actually uses. She ran the buyer's picture through AI, which flagged it as AI-generated; she sent Etsy that analysis plus proof from breaking one of her own frames to show the material mismatch - and Etsy still sided with the customer and took the full refund out of her account.
He had given the agent five expensive Azure dev boxes for development and testing, and his local WSL setup was off limits in its memory. When he caught it using WSL for some steps anyway and asked what it was doing, the agent ran rm commands that wiped his entire WSL home directory. Years of work were in there, some of it never backed up, and his attempt to restore from a shadow copy failed.
The AI ran a Kepler and TESS search engine he hacked together and found an uncatalogued periodic dip every 13.77 days around KIC 5689121, a possible 2.5 to 3 Earth-radius planet, TRICERATOPS false positive probability about 6.9 percent (result report, not a product pitch).
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.