Opus wrote his grammar language in OCaml in an afternoon and fixed his examples
The AI wrote a working OCaml implementation of his PEG language the same afternoon, fixing several bugs in his example grammars.
A random mix from the whole library. Shuffle for a new set.
The AI wrote a working OCaml implementation of his PEG language the same afternoon, fixing several bugs in his example grammars.
A Japanese creator in vocational training had the AI analyze her past articles' tone, draft two note posts and build a review board with cover-image briefs; both posts reached scheduled publication with only her OK. The one step the AI could never complete was uploading the cover image, because the OS file-picker dialog is unreachable to it, so that step stays manual every time.
Since July 2026 a Japanese creator has run a political clip channel with a pipeline the AI built: it watches source channels, fetches new videos, transcribes them locally, picks highlights from voice peaks and wording, fixes subtitle typos and names, makes thumbnails and titles, exports long videos and Shorts, uploads them unlisted, then collects view and retention data to feed the next round. In 3.5 months it shipped 319 videos for about 1.05 million total views and 1,080 subscribers, though the median long video reached only 268 views; he publishes the failures too, including the agent claiming 'fixed' when it was not.
Using Figma Console MCP, he took screengrabs from an iOS app he is building and had the AI build the static images into editable Figma frames. He says it worked.
After WordCamp Rajasthan 2026, he rebuilt a full WordCamp event site with AI: pages, header, footer, a mega menu, Contact Form 7, Popup Maker and a custom post type. Six videos show the steps.
Wired up a replacement for needed functionality with AI over a couple of weeks, avoiding tens of thousands of dollars in recurring yearly costs.
A Japanese YouTube creator's paid note documents the AI system he built on Oct 13, 2026 and runs on his own account: scheduled tasks pick a topic from his idea notebook, write the article to his style rules, generate the header image inside the built-in browser, publish to note, announce on X, then record views and send a nightly report. In its first three days it published three articles at noon daily. Twice on Oct 14 tasks stalled because reopening the AI had logged him out of note and X (he published manually that day); the nightly report task itself flagged the logout. He states plainly there are no view or revenue results yet.
The company that made his vinyl plotter no longer exists, and its basic software needs an online check in that no longer works, even though the plotter itself is fine. He reverse engineered what the firmware needs and vibe coded a replacement graphic editing and cut planning app. He added features he had always wanted the original software to have, and says it now works better for him than the original did.
He builds a Minecraft hosting platform on his own and runs AI around the clock as his chief of staff. It spins up agents for research and bug fixing, works from a rules file and a private record of every decision and mistake, and leaves him a short report each morning. Last night it caught an error hitting visitors from Instagram, shipped a fix, and caught a users failed backup restore and fixed that too.
At work he prompts LLMs to write extensive tests for legacy modules, rewrite them cleanly, and pass the tests again; users report the software suddenly responsive in under a second and customers are happy.
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.