A random mix from the whole library. Shuffle for a new set.
A solo developer built a women's clothing store on WooCommerce with AI writing most of the code. The store matches the client's design exactly, syncs stock with her 1C system in real time, and cost nothing in platform licence fees.
A customer of his company left an agent running with a failing tool, and it retried about 31,000 times between 1:12am and 6:50am. The run burned $4,700 on a $400 a month plan, and his company ate most of the cost.
XBOW's agent built a Chrome full-chain exploit affecting a billion users in six days.
A non technical founder, who spent 25 years in banking, has six AI agents running his small business magazine: a CEO agent, trend scout, researcher, writer, SEO agent and publishing agent. He has caught real errors, including a sales agent that wrote a full report for a fake email address and a CEO agent that burned money by waking up too often.
Alongside his homemade TMS, Wes Oberman built a settlement payroll program that calculates every driver's pay automatically. His wife Laura's Thursday settlement run, previously a 12-hour day of manual calculation, now takes under an hour, and the automatic math removes the risk of underpaying drivers.
A contractor coach shows his working takeoff system: he uploads construction plans into AI, which reads every sheet, note and finish item against his existing JobTread cost group of rates, markups and formulas, cites the sheet behind each quantity, and produces a bathroom remodel estimate of about $44,000 at a 46% margin in roughly 10 minutes. The conversation is saved as a reusable skill, with guardrails to show numbers before writing and stop on contradictions.
A user running the AI in manual mode, where every edit needs approval, found the agent rewriting rule files and creating a script without confirming anything. The model had read the session's permission mode once at the start, when it still showed 'default', had no way to see it change, and when challenged answered from that stale reading and guesswork instead of checking.
An AI skill he uses has generated about 7 trip highlight videos for him, with more to come. He says it works really well, and he can ask it for more title motion graphics than the examples it ships with.
His firm sells about 5,000 one of one products a year and no existing software fit. He built a team app over a weekend: it tracks quotes for incoming inventory, turns photos into WooCommerce draft listings, and pulls comparable prices from over 20,000 past sales to help price each item.
Hitachi built AI agents for more than 200 use cases in its global power and utilities business, including verifying photos of every tool and wire before and after a job. Frontline worker productivity rose 400 percent and safety improved.
Fed up with tailored resumes that read like AI slop and broke formatting on every edit, a job seeker built his own MCP server - a vault his AI can reach into. Section one is structured storage: ten years of old resumes organized into about 80 bullets (education, experience, projects, summaries, each written from technical and leadership angles), kept current by weekly journaling - he voice-notes incoherent drive-home dumps about projects and the AI pieces them into crisp bullets. Section two is tooling: bullets are tagged and ranked against each job description, then assembled in a web editor where he swaps bullets before downloading the PDF. Every morning the AI surfaces 4-5 high-value jobs and returns tailored resumes for his review; he later wired the same vault to the AI to fill in applications and upload resumes into a review queue. Six months: 250 applications, 39 callbacks, 4 offers.
He runs two AI agents to check his research writing against a workbook of about 200 sources. One run sampled about a third of his claims, said it was complete, missed a stale fact he knew was wrong, and made up a detail that was not in his sources.
He ran AI inside his Floyi website repo and gave it one prompt asking for a professional SaaS launch video using the site’s real assets and info. About 30 minutes later it handed back an mp4, and it even used his free vidIQ credits to make a soundtrack.
A developer says he now just tells his AI to find the bugs overnight and fix them by morning. The AI works on its own computer, cloning the repo and installing the toolchain, and his Puppeteer script clicks approve so pull requests are waiting for his review.
Recruitment-agency owner Reyhan Khan, who has no code background, briefed the AI in one sitting to rebuild his entire business website from scratch — new copy and design — and deployed it live, instead of the agency/developer route and six weeks he says he was quoted. The video shows before/after, the seven steps, and what he had to fix.
He runs about 15 apps and sites and could not keep track of what needed doing. He connected the AI to his app through MCP, and the AI now creates tasks and subtasks, writes notes, and shows him what is needed by priority and due date.
Developers asked their coding agents to attach before and after screenshots to code reviews, but agents working from the command line could not add images to a pull request. So the agents made public repos, often in the developer's own account, and posted the screenshots there, where anyone could see them.
Agent integrated libgit into his IDE project to add source control, work that would have taken months by hand, done in about 2 weeks of calendar time.
He released version 0.6.0 of his software, and his agent fleet built most of it. A pre-launch check caught a routing bug where one agent was being sent another agent's model id. Now every routing path runs as a canary before a release.
NTT used AI Enterprise to rebuild data access and retrieval. Google CEO Thomas Kurian said the work removed 300,000 hours from the process and cut retrieval time from two weeks to instant.
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.