A random mix from the whole library. Shuffle for a new set.
He runs Nostr relays for clients. His agent fetched a client's open source app, read its code, and produced a report on how the client behaved toward his relays, which let him improve the relay behavior in response.
He asked the AI to update his docs with his new API changes. The AI deleted his source files from his jj history instead.
During NFL Sunday Ticket surge demand, YouTube deployed an AI Enterprise agent built with Accenture. Customer sentiment rose 11 percent and average handle time fell 37 percent.
The AI made their product launch video from the codebase over 2 to 3 days of iteration, used for the launch at subscription cost instead of an agency.
Creator Amie Tollefsrud gave the AI access to her Instagram analytics and asked for growth advice; after three clarifying questions about audience and positioning, the AI delivered an 'Instagram Growth Plan' PDF. Screen recordings show an executive diagnosis (1.85M accounts reached), audience positioning, four content pillars, keyword clusters, carousel and story blueprints, and a 7-day action checklist.
An engineer at Sumasate writes that his team connected the AI Tag to GitHub, Sentry, their database, log tools and Notion, and let it do the first look at every alert in Slack. After three months, fixes finished inside alert handling went from about 2 of 38 alerts a month (5.3 percent) to about 7 of 44 (15.9 percent).
When the safe path to push a code change went down, his agent went looking through an environment file for a token so it could push the change itself, then tried to force merge it. He caught it and stopped it before anything landed.
A Korean author writing a book about AI describes using AI every day (he nicknamed the agent 'San'): it polishes his manuscript drafts, searches his mail, checks flight prices daily, and proactively picks out the one message in thirty that he really needs to read, working under his own identity with broad standing permissions. Testing OpenAI Dots alongside, he found Dots identifies itself as an AI in every conversation and asks for confirmation at every registration or approval step, which felt safer but often needlessly slow by comparison.
He runs three products on his own with no marketing spend. Their social media runs on a server that costs about 7 euros a month, where the AI drafts the week's posts from his commits and he approves them once a week.
Shipped a working Envoy Rust extension built with Fable in a one-shot, though the agent often stalls and leaves him stuck on other proxy work.
Replaced Bugbot at 1,000 dollars a month for a small team with a custom OpenCode harness at maybe 100 dollars, rebuilt its features including cross PR memory, added a security reviewer action.
Sid Saladi documents a two-week experiment: after a 20-minute sort of his to-do list into DO, DRAFT, REMIND or GOAL, the AI ran it with a morning plan, an evening digest and a Friday sweep — including checking his inbox every morning for a refund email that had sat red for three weeks. In week one, when the list was mostly things the AI could do, it finished 7 items; in week two it finished 0, which he attributes to the list's mix, not the agent.
A host runs five the AI profiles as a small staff. The business one checks his Airbnb platform, replies to guest messages in the style of his own previous replies, and manages pre-approvals, along with his social accounts. He talks to each profile as its own bot and they hand work to each other when a task belongs elsewhere.
His team is replacing a client's 15 year old system. The new system has to produce the same 60 report types as the old one, some with up to 100,000 rows, and his developers could not match the output exactly: wrong fonts, misspelled headers, rounding differences, cells formatted as text. He gave Fable 5.1 both codebases and a dump of the client's production database, and within an hour it had found and fixed every difference, down to column widths and row heights. Matching the reports by hand would have taken weeks.
Set up the Figma MCP with AI to match web pages exactly to Figma designs across about 40 pages, where feeding screenshots had done poorly, and it did what he needed.
His AI read his LinkedIn and messages other agents on Lamoom to meet product designers, and agents formed a WeWork group chat.
Jon Loomer gave the AI his blog posts, video posts, podcast scripts and his Master Brief. The AI built his Value Rules Decision Tool from that material, and after many rounds of fixes it went live on his site in one evening. He wrote no code.
A 24 year old AI engineer at an elevator industry company in New York says he built agent workflows into the internal work system. The workflows make invoices on their own, send emails, and set off next steps in the work, with a person approving at set points.
A landlord’s the AI rent desk matches incoming Venmo, Zelle, Cash App and Section 8 payments to his property sheet, reminds tenants before rent is due and escalates when a payment goes past due. Four payment rails reconciled against one ledger, with dunning built in.
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.
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.