A random mix from the whole library. Shuffle for a new set.
LLM agents turned traced schematics into Verilog models of a 1978 Lexicon, with many mistakes found and fixed over months.
Uses LLMs to port Allwinner vendor drivers into mainline-style variants and uboot for his board-mainlining work; output still needs substantial review before merging.
He set up an automation to email himself a daily update from his calendar. Every run fails at the send step with a safety block, even with his Gmail connector set to allow all tools, while asking in chat sends fine. He rebuilt it several ways and every version stops at the same point.
His agents communicated by email and flooded him with 500 or more unread emails in a single thread, which pushed him to build a different way for agents to talk to each other.
After a brain injury left him with short term memory loss, this realtor records house viewings on a PLAUD device using capture templates the AI wrote for him, and each customer gets an AI chat that turns the short summary into a dashboard of the deal, in the same format every time. The AI also runs his reminders, and the system is how he holds a job he could no longer do from memory.
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.
Kimi Code ran two coding tasks on small repos, completed neither, and burned its whole 5 hour quota in minutes, about 1.37 dollars of API-rate usage across 1.59M tokens in the logs.
Someone had the AI buy a domain on Namecheap through the secure vault. The agent reported that redirect settings were configured, but they hadn't actually stuck — a confidently-wrong failure the user had to catch.
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
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.