A random mix from the whole library. Shuffle for a new set.
He made an Easy Chores list on his Trello board and a skill that teaches the AI to find more of them in his backlog. The AI fixes them in pull requests, and the chores get done instead of sitting in the backlog.
He asked the AI to scan his entire work inbox and count emails from accounts he had never sent mail to, so he could weed out newsletters. It came back with two, which he knew was wrong, and when he asked why, it said it had only looked at the 25 most recent emails and given up.
A contractor onboarded Instinct through a WhatsApp chat that simply asked what he had been putting off; it now prepares his contracting invoices and drafts his outgoing emails - the two admin jobs that used to pile up behind the actual work.
He is not a developer. He built an agent he can talk to that tracks his invoices and costs of goods, reconciles inventory and writes reports, and pushes back hard when a project goes over budget. It started as an artifact and he moved it to Cloudflare so it lives on his phone. He is now thinking about making it a tool for his whole industry.
Agent acted as a dogged advocate in a commercial dispute and won it.
Author educator Christopher Kokoski set up a test the AI with a series bible in Google Drive for a mystery series (hero Rudy Relish: seven hard rules including a bad left knee, never touches a gun, no ketchup on the cart). He added the first three chapters of book four and had the AI check each against the bible and all other pages, on a daily scheduled check. Chapters 1-2 were clean; in chapter 3 the AI caught every one of several mistakes he had planted, including one he considered an unfair plant. (Test manuscript on a fresh account, run for a week.)
His todo list outgrew his Obsidian file, so he moved about 300 issues into Linear through the AI. He then refined the roadmap by talking with AI while driving.
On machines that regenerate their machine ID at every boot, journalctl reported no journal files even though logs existed, because journald and journalctl end up looking in different directories. The answer links a fix script that Opencode mostly wrote, published on GitHub with a full write up of why the race happens.
The creator had a business idea and a crew of AI agents built the entire Redd Walks platform, including the website, the iOS and Android apps, SEO, outreach and tracking, totalling 643 pages with real payments and checkout. The product is audio tours of Madrid in 7 tours and 8 languages, with two apps under 3MB, and the creator also shows four blind spots the crew could not see around voice, repetition, order and live testing.
A developer runs his own repos and production server under a written constitution file in every repo. Automated runs check production logs daily and file bug reports. When he types one short check in message, the system scans and ranks his open issues, sends sub-agents to fix the top ones, and code deploys to production twice a day without him pushing it. A read only agent on the production box acts as his dashboard, checked through a chat app.
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.