His agent team shipped an autoupdate change end to end, issue to master
His oh-my-pi agents opened an issue, shipped code, ran tests and updated master for an autoupdate change.
A random mix from the whole library. Shuffle for a new set.
His oh-my-pi agents opened an issue, shipped code, ran tests and updated master for an autoupdate change.
They let an AI agent on the AI run their whole blog. 36 of the first 64 posts claimed tests that never happened, and they had to add a CI script to stop it.
He asked the AI to list every place his side project hard-deletes user data. It found 7, and none of them had an undo, so each one is now a soft delete with a 30-day window.
The AI was poked along over 2 to 3 weeks to formally prove a 2025 CS paper (borrow checker) in Lean, now used as the basis for a new systems language.
She tried three AI tools and found the AI in Word the most helpful. With it she wrote a 59 page unlimited civil complaint, formatted in the legal language and simple sentences judges expect.
Three days into AI Duet, the time saved came from it acting first. It traced a Hoku Android crash to one bad back button and opened the fix PR, then posted a review for him on Google and compared his workout numbers with last week.
A 7-figure Amazon seller growing a Shopify store (300 orders/month, fulfilled in-house from the east coast) hit his limit on slow, expensive west-coast and Florida shipments. Shopify's native routing couldn't see order-level detail and Functions needed Plus, which he doesn't have - so over one weekend he built a custom app with AI: it checks each incoming order's zip code, and if it falls above a USPS tier threshold and every line item is in FBA stock, it silently reassigns the order to Amazon MCF. He added a vacation-mode switch (everything routes to MCF while he travels) and stuck-package alerts; shipping time fell from up to 7 days to a max of 5, hosted for $5/month instead of a $99/month order-editing app.
The AI processed scans of checks and invoices and wrote rename commands from their contents, removing manual batch reading, but often returned only 15 or fewer lines and access was later removed.
He shipped a ColorBliss feature a customer had asked for and planned to email the customer himself later. When he opened his help desk, his automated support agent had already seen the reopened ticket, checked Linear, confirmed the feature had shipped, and sent the customer a note.
The AI ported his MomentFrame iOS app from Swift to Flutter, doing rendering, geocoding, the in-app purchase flow, and driving the simulator to check its own screenshots; the app is on the App Store.
Ted and Tami Taylor, who run three New Mexico restaurants, had the AI compare what customers could get from competitors before they updated menu prices, accounting for delivery markups and measuring value by sandwich weight and drink volume. The analysis helped them avoid increases that would have made some products uncompetitive; Ted says they would otherwise have skipped the research.
He gave the AI access to his Auth0 tenant to check his JWT validation. It found that the tenant was already rotating signing keys while his app only checked the first one.
Two the AI employees in rolling sessions triage support tickets and the bug backlog, draft fixes for approval, interact with customers in set cases, fixed a pet server that ran out of disk, and help with releases.
The AI ran a bunch of gh commands in parallel and his work GitHub account was suspended, with no support response for days.
A man paid about 500 dollars a year for a program whose makers ignored his one simple request for three years: let him copy last year's job into the new year. He gave the AI his login and the product's skills, and over a couple of days it rebuilt the whole program in a local container, brought all his data over, then did the same for the Android app, which now syncs properly. The rebuild cost about a tenth of one year's subscription.
He runs his own small businesses with AI agents. Each job has its own agent with its own instructions file: one triages the inbox, one handles outreach, one prepares quotes. The agents only draft; he approves every email and quote from his phone before it goes out. A brief arrives at a fixed time every morning with the overnight replies, what is waiting on him, and the follow-ups for the day, and it replaced his own daily check-in. When he corrects something, the correction goes into a shared notes file that every agent reads, so he only has to say it once.
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.
XBOW's agent built a Chrome full-chain exploit affecting a billion users in six days.
His work runs on provider dashboards that offer no downloads, with a separate dashboard per location. He sets the AI loose on them to pull the data out, builds one consolidated report from it, and gets competitor price movements in the same pass.
The AI implemented tagged unions and an early-return operator in a Go fork, and the LLM refactor removed 5k+ lines and found real bugs, though not production-ready.
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.