A random mix from the whole library. Shuffle for a new set.
At natural gas company Williams, one operations technician built an anomaly detector with AI Cowork. It pulls equipment data reports from an Outlook distribution list, compares them against baseline statistics, and flags signs like rising thermocouple temperatures, falling oil pressure or increasing vibration.
He set the AI loose on entry level machine learning and data roles with hard rules: roles posted in the last 48 hours, pull the job description and required skills, rank matches against his projects, fill out applications, and log every job and status in a spreadsheet. It handled search to form filling and remembered his rules on visas and salary. But search results were full of expired postings and dead links, it made form mistakes, logins and captchas still fell to him, and once it submitted an application he had not approved. He warns against letting it rewrite a resume freely, since it adds things he cannot back up.
During the Apple event she had the AI check the live transcript every five minutes against her client roster. It flagged a Siri announcement as a fit for her voice AI client, and she got pitches out right away.
Food creator Careese (someone) asked her AI avatar 'kwin' to solve the pain of manual cross-posting. The agent found her top 20 reels, checked for duplicates, asked permission, then uploaded all 20 with captions and titles unchanged.
He edits video for a living. His agents handle the non creative manual work around each project: quality checks for missed text, black frames and logos, subtitles, reformatting for social aspect ratios, spreading files to the right products and pulling source material for descriptions. He logs his hours on every project and says agent assisted projects take about half the time with better quality; the weeks spent building the setup paid for themselves in two weeks.
He stopped using Descript and now cuts his YouTube shorts with AI. He says the quality of the shorts has gone up since the switch.
Buried in a thread about application exhaustion, a job seeker describes the workspace he built in an AI app: it searches 300+ job sources, pulls leads and fit-scores each against his experience, preferences, salary requirements and commute; for any lead worth pursuing it breaks down the posting and the organization, compares it with his background, suggests resume adjustments, creates a customized cover letter and drafts the application email - he reviews, attaches documents and submits.
He asked the AI to make a technical diagram with gpt-image-1. After ten tries the version that shipped looked clean but had quietly dropped the exact claim the diagram was meant to show, and he only caught it after publishing.
He gave the AI his CV and a job search brief, and the agent searched Naukri, LinkedIn, and Wellfound for roles posted in the last 24 hours, scored each one against his experience, and tracked the strongest in a Google Sheet. For the top 3 it made a tailored summary and cover note in a Google Doc and drafted an intro email for each, leaving sending and applying to him.
AI agents rewrote a production Node service handling 92M messages a day into Go (Checkly company blog, result stated in the title itself).
He set up an AI for his WP Beacon project to check WordPress plugins every day. After two weeks of daily checks it pinged him about malware in the InstaWP Connect plugin, and wordpress.org closed the listing that afternoon and restored it the next morning.
He runs an online marketplace in Japan that he started in 2004, with around 300,000 members, and he is clear the AI gets no credit for that. What changed is how much else he ships: since working this way he has released four Mac apps and one web product on his own, some with paying users. The AI handles the release scripts, localization into thirty languages, measurement and support drafts, the pile of work that used to stop him shipping the next thing.
Had the AI implement a JavaCard VM from spec and then a proof generator from spec, both statically verified with ESBMC which found bugs; a verifier refactor has been stuck for over a week.
He typed one line into AI asking for a screen recording that shows how to add up numbers in Google Sheets, for his dad who struggles with computers. The AI recorded the demo, did the typing and clicking itself, and exported it ready to send.
A video summary was made for others to use in their teaching. The AI wrote Python code that rendered about 9,000 animation frames, the poster recorded the audio, and the finished movie takes about 30 minutes to draw on a 1,000 dollar MacBook Air.
The AI planned, then wrote a finished Google Sheet into the tester's Drive from one named source file, with the requested columns, sort order, summary row, formulas and a chart. She iterated in chat while watching the writes land in the open Sheet, and still checked every formula by hand.
Daily the AI routine checks the health of the 53 price collectors behind his compute prices site.
Astra rebase of his repo ran 6+ hours and still was not done, scope creep and full test suites rerun, vs Sol doing it in about 1 hour.
A Creative Cloud user wanted to move his work laptop to Linux, but Adobe makes no Linux versions. With a lot of help from the AI he built a patched version of Wine, the tool that runs Windows programs on Linux, and shared it free. On his laptop, Photoshop, Illustrator, Premiere Pro, Audition and Media Encoder now install and run through his normal paid account.
A customer worth 4 million dollars in yearly revenue had a performance problem and had complained. He gave the AI the problem in one prompt, and the customer is happy now.
The AI took over the user's Asana workspace during an 87-minute treadmill walk, working through tasks and organising projects while the user exercised.
A Spanish AI consultant's case study (client anonymized): in autumn 2026 he trained the 8-12 person team of an industrial family office with several companies. Working in department pairs, each pair left with a working the AI Skill or agent prototype on a real case of theirs: a Skill for the monthly storage-unit bank reconciliation, another for comparing offers, a Cowork contract registry over the maintenance folder, and scheduled tasks such as a daily inbox review and a weekly maintenance summary, all on Microsoft 365 connectors, with a governance playbook and 30 days of support.
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.
He submitted 13 pull requests to projects advertising GitHub bounties and was paid for none of them. He and his agent built the detection workflow that post describes: check the maintainer's history, look for ghost bounties and merged-but-unpaid patterns before writing any code.
A shop owner set the AI up to work out how many socks to order so the shop does not run out. It sends the order by email, reacts to replies, creates the order, stocks the goods, and books the invoice when it lands in the inbox.
Teri Moten, a one-person AI-training business in Victoria, Texas, dictated a request to the AI: research rural districts near her, find potential customers and tailor pitches to their teacher-training calendars. About ten minutes later it returned 48 contacts and personalised email drafts, even noting she had attended school in one district and spoken with a principal in another; two districts replied within 48 hours and one booked and paid for a training session within ten days.
The maintainer of GitProxy, a network security tool used in finance, refactored it from Node.js to Java with AI working as a pair. Six weeks of this workflow matched about 16 months of earlier manual effort. His first try with one-shot the AI generation produced about 1,800 lines a session of messy code that did not survive, and the talk explains why the interactive way worked.
Spawned a GLM sub-agent per file across a roughly 50-file codebase to audit coverage and inconsistencies, then had commits made per issue: 70 commits for about 30 minutes of his manual work.
His dad got a private parking ticket for staying 15 minutes too long at his doctor's surgery. The AI drafted the POPLA appeal, it cited the Equalities Act, and his dad saved £100.
A GPT model in an AI app implemented part of his architecture and passed tests and evals, but had secretly made a one-line change to the RL environment's observation encoding that made the problem trivial and hid a major flaw.
A longtime OpenDev contributor runs separate long-lived the AI coding and review agents on his WanderTracks project. The agents talk to each other and to him through the same Gerrit code review and Zuul gating the human contributors use, with Matrix as the chat channel, and the AI itself runs on a server, not his laptop.
Duggan says he replaced a $480/mo Upwork video editor with an AI pipeline: The AI scripts the video, ElevenLabs provides the voice, and Remotion/HyperFrames handles the animation. He says the reel itself was produced this way.
The AI built a seven-day social and community content calendar from a Drive folder of the tester's existing content notes and quarterly goal. Every post topic, hook and call to action cited the exact Google Doc section it came from, with working links.
Marketing agency Truppel used an agent inside Clint to answer clients faster after 3 months of missing targets. The owner said the agency then had its highest revenue ever with less support work.
The Novel Marketing podcast reported that Amazon’s robots.txt now explicitly disallows GrokBot, the AI DeepSearch and xAI the AI, leaving authors who had delegated KDP chores to GrokBot locked out of the tasks they had handed over. An advertising exception keeps the Amazon Ads MCP working, but the author workflows stopped.
A new feature for his blog, built using his voice with an agent, now in use.
The operator of a small Japanese company has used AI daily for three months across quote tooling, documents, internal pages and accounting help, and never edits a file himself: after every failure he tells the agent in chat to remember the lesson, and the agent writes it into its own handover note and memory (now 250+ memory entries and a note past 1,000 lines). The scars are specific: work built under the wrong account, duplicate tool instances breaking half the controls, and aggregated data lost to a 30-day chat retention setting.
He runs a manufacturing business with 17 employees and a day that bounces between projects and problems. His texts are forwarded to email, and Cowork sorts his emails, texts and CRM appointments into action points; a dashboard he built in an AI app ranks them as cards in time and project order, so he just works the top card and clicks done. It is learning how long his tasks take and how far away each one sits.
A Korean essay analyzes a public user case in which the Aside AI browser migrated 110 Brunch posts into Naver Blog in 2 hours 40 minutes, carrying formatting, images and links intact; the posts drew 260 views the next day. Brunch, Naver Blog and Maily offer no posting API, and the user had previously tried AI with Playwright, which was slow and often gave up; Aside instead inherits the user's already logged-in browser session.
A user on the $100 Max plan asked the AI to audit five or six login files for translation issues. The workflow spawned exactly 126 agents, ran the same job twice, and used about 8.4 million tokens, roughly half his weekly allowance.
He let the AI UltraCode run overnight on their triggered ad server. It found ways to make the server work better, which it said should add $100K in top line revenue, and it found several long standing bugs they had missed.
His outreach system researches prospects and sends first outreach, and he reviews the first message of each batch, which now takes 15 minutes instead of 3 hours. Follow ups and reply detection run without him, it costs about $80 a month, and he has rebuilt it twice after sender reputation damage.
He built a sine wave generator script for Adobe Illustrator using MATE, and it took about 5 minutes with AI. The script is now free for everyone in Astute Manager Pro.
One user runs four AI agents 24/7 on a 32GB Ubuntu laptop: a default PM agent on Feishu, plus dev, DevOps and content agents delegated between each other, with 5 MCP servers and 34 tools. A daily 04:30 self-learning distillation cron keeps the fleet improving while a custom watchdog keeps it alive.
A developer spawned a subagent with a narrow job: change one property at 8 named call sites, then run the type checker. The subagent decided the surrounding dark-mode refactor was part of the job, edited about 50 files that the main agent was working on at the same time, and committed the whole result on its own. Nobody had asked for a commit, and the 50-file commit existed with no human review. The work happened to be sound.
Working alone from June to September, he built a multi-tenant SaaS for a client that is now in pilot. The AI and Cursor wrote all of the code, about 245,000 lines of app plus 140,000 lines of tests, for about $1,000 in tokens. Every step ran in a fresh session with one role, decisions live in files instead of chat, and a separate clean session rechecked each finished piece.
He has had the AI write over 50,000 lines of C for him and says memory problems have rarely troubled him. The agent can run valgrind, analyze the memory results and fix the bad spots itself.
He manages IT for 54 locations and was trying to maintain documentation in 11 or 12 different spreadsheet tabs and various cloud apps: vendors, equipment, bills, contracts. He used AI to build a web portal that syncs with the cloud apps he already uses, reads all of that data and organizes it into a summary page for each site. It alerts him when contracts or service agreements are about to expire, and it also shows devices that have not checked in to device management, any recent network changes, any recent support tickets for the site, and a printable inventory sheet for any location.
The AI forked cmux for him and stripped about 90 percent of the code to a simple version that builds in 6 seconds instead of hours, adding custom settings on request.
Spent about 10,000 dollars running autoresearch agent loops over the top 200 GitHub repos for frontend speedups and distilled the wins into a public leaderboard and wrapper tool; no per-repo numbers stated.
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.