A Japanese Threads creator split his account's operation into six AI agents with one deliverable each (researcher, writer, poster, fetcher, analyst, supervisor) and reports 1,181+ posts and over 10 million cumulative impressions. The writer agent may only cite numbers stored in a single 'truth file' so it cannot inflate results, the poster must confirm the published URL rather than the button click, and the fetcher records 'not retrieved' instead of zero when a fetch fails.
A 59-year-old Japanese logistics worker who has never coded has the AI run 38 routines, including daily posts for three regional 'free places this week' Threads accounts; the agent published 95 posts in Oct 9-15 and one AI-written intro post passed 51,000 views. He reviews output five minutes morning and evening from his 4.5-hour commute.
During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.
This one went wrong. See what happened before you try it.
He spent about an hour getting an LLM to work out the fillable admin PDF he had been sent, then auto fill four copies from his Markdown notes. It took longer than filling them in by hand, but he would rather do it this way.
Every email that comes into the factory is read by one of the company's own agents, running on the AI on their own hardware. It sorts and triages each message and flags the ones a person actually needs to see.
He built an invoice processor for a small law firm: PDFs arrive by email, get read with OCR, matched line by line to case codes, and pushed into the billing system. Anything it is unsure about goes to a manual review queue with a screenshot, and months of edge cases like 8s read as 3s went into its rules.
Every release of his app used to cost him a weekend taking store screenshots in 16 languages, cropping them and pasting them into store cards. He and the AI built a small tool that drives headless Chrome through the real app, grabs the screens in each language and composes the finished cards with captions and backgrounds. A release is now one command.
He let an AI run his HighLevel affiliate site for two weeks. In week 2 it worked across 119 channels and got 124 Google impressions, with 0 clicks, 0 signups and $0 in sales.
This one went wrong. See what happened before you try it.
A delivery driver has the AI run his weekly payroll. Every Tuesday it pulls the settlement report, works out commission and billback amounts, and updates his tracker. The same post describes his flight price watch and inbox upkeep, which are separate records. He says the payroll job used to eat a chunk of his evening.
The creator of Babylonian Twins had the AI port his 2010 game engine and the original 72,758 lines of 1993 assembly into Godot. The Definitive Edition is live on iOS and Android, the 1993 original is free on itch.io, and a fix found from a one star review shipped as version 2.0.3.