A Korean AI educator split his Naver Blog automation in two after learning Naver blocks the AI’s browser tools by policy: The AI drafts posts into a queue file on a schedule, and a Playwright script on his own computer publishes them daily via launchd. Three real editor errors (ignored paste events, a near-duplicate insert, a hidden reserve-publish button) are documented with fixes.
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.
This one went wrong. See what happened before you try it.
He manages his work photos in the cloud version of Lightroom and only used Photoshop for simple white background work, so leaving Adobe felt hard. Lately he has the AI do everything from organizing his photos to batch editing them, and Lightroom is down to moving photos into albums and exporting them all.
He and a colleague used AI to transcribe over 28,000 documents for the Papers of the War Department project. They wrote up how they did it on the RRCHNM blog.
The AI CEO agent and sub-agents run one of his side hustles daily, pitch ideas each morning, and implement the chosen one via PRs; revenue up 4x in the past month.
Creator Alex Finn recounts on a podcast episode that he gave an AI access to his business inbox and told it to answer and negotiate with legitimate companies. Within about four hours it had researched market rates and closed its first sponsorship deal, worth $10,000.
Haiku 5.5 subagents read 206 of his own AI sessions and kept 223 verified failures, many of them breaks of rules already written in his instructions file. He built eight hooks from the failures that catch about 30 percent of them, and 138 failures fit no hook at all.
This only partly worked. Worth knowing before you try it.
A vendor told him he needed Windows only software to flash a board for his hardware project, and the open source option could not erase the board after the first flash. The AI reverse engineered what the Windows software was doing and wrote a Python script with the handshake and erase command, so he could erase the board from Linux and then flash it with the open source software.
Jon Udell recorded himself doing a final audio pass in Bram Studio, then had the AI draft a screencast from the capture. The AI used FFmpeg, Apple's Vision framework, the Swift compiler and Bram's timed log to make a tightly edited two minute video that picks out and labels each use of FFmpeg.
She gave the AI control of Chrome through Warp and told it to learn the interface, click around, and leave key frames and an mp4 on her desktop. She used to spend hours recording short demo videos herself, and the quality was worse.