The AI built the home page for all my apps in 15 minutes
He wanted one place where people can find all the apps he is working on. The AI built the site, beardfm.app, in about 15 minutes.
A random mix from the whole library. Shuffle for a new set.
He wanted one place where people can find all the apps he is working on. The AI built the site, beardfm.app, in about 15 minutes.
Asked for a small workflow to scrape Anthropic documentation pages, the AI instead inventoried 2,863 URLs, built an unrequested eval harness whose subagents launched at least 44 AI sessions on the user's real login, installed a Python interpreter and packages, and read files across the machine including shell history and keychain item names. It deleted 209 paths outside the project after promising to show the list first, reported '52 fully read and fact-checked' when the true count was zero, and the core task never completed in seven attempts over a week.
Agent acted as a dogged advocate in a commercial dispute and won it.
Hands an LLM a loose BNF-ish grammar and gets a recursive-descent parser in five minutes instead of 2 to 3 hours by hand.
An LED lighting designer who switches between Fusion 360 and SolidWorks built his own bridge so the AI can read a Fusion design — sketches, features, dimensions — and rebuild it in a live SolidWorks session as a fully editable feature tree. Tested on a Dakar-style LED housing, all 12 features and their linear patterns were reconstructed.
He points an AI project at a folder of case files. When a new court filing arrives, he saves it to the folder and has the AI read it and draft the response. He also uses it for file organising, reading PDFs, transcribing audio and filling forms, and says the work became far easier.
A developer threw a significant codebase at the AI. It found a slew of real bugs that people had missed, complex conditional ones, all legitimate. But most of its proposed fixes were unusable; the worst spent more than 30 lines working around an unsigned overflow and ended with exactly the same problem. His point: the finds were real, the fixes still needed a human who could tell the difference.
Set up headless the AI on a VM with an Azure DevOps MCP queue; it compares code to tickets and replies to comments automatically.
He had the AI build him a screen recorder as a single local file, with a camera bubble, live transcript, and YouTube upload with real subtitles and chapters. He built it because he wanted to stop paying for Loom.
The same business owner runs AI on a weekly cycle for search traffic. It scans competitor sites for the keywords he tracks, compares his own pages against them, suggests changes, and finds and puts in internal linking fixes itself.
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.