An AI routine reads his app's errors daily and posts a plain digest to the team chat
An AI routine with only Slack and Sentry MCP access reads Sentry errors, compares them to the app source, and posts a daily digest to Slack; reports very accurate.
A random mix from the whole library. Shuffle for a new set.
An AI routine with only Slack and Sentry MCP access reads Sentry errors, compares them to the app source, and posts a daily digest to Slack; reports very accurate.
Andy Bennett built Helm, a Mac, iPhone and iPad job tracker with CV tailoring, with AI writing all of the code and most of the design across 641 commits and 21 plans. The first working Mac version landed in about eight hours of commits on September 11; both apps are now in TestFlight beta.
His agent researched a prospect and sent the email. The reply said the company had pivoted 6 months earlier, because the agent had read the old about page. The research saved him time, but the stale facts cost him the reply.
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 is a sales manager who does not code. In five weeks he built a system that connects the AI to his CRM, Microsoft 365, his reMarkable and his Plaud recorder. It tracks meetings and calls, updates his todo list, drafts follow ups and puts them in his calendar, imports business cards, prepares quotations, keeps the CRM updated with meeting reports, benchmarks his prices against competitors, sends personalised mailings, and every night reads the day's email and prepares a recap of the next day.
A builder runs AI as a night shift for his side project. Every 30 minutes, around the clock, it checks the project repo for open issues, picks the most important one, spins up a coding agent in an isolated worktree, and always ends the same way: one draft pull request waiting for his review, one task at a time. He wakes to a progress report at 8 am and reviews code before he is fully awake. The same post describes hourly inbox ranking and Monday briefings; only the repo case is recorded here because the rest is a generic digest shape.
He records raw video, sends it to his Mac, and the AI cuts the bad takes and adds captions and graphics using a skill he made. He says he does not open a video editor anymore.
Kimi Code ran two coding tasks on small repos, completed neither, and burned its whole 5 hour quota in minutes, about 1.37 dollars of API-rate usage across 1.59M tokens in the logs.
He has the AI edit his YouTube videos end to end. It transcribes them, cuts the dead air, zooms the jump cuts, adds lower thirds, sound effects and music, and hands back a Premiere timeline.
His business was paying Stripe 4,633 euros a year to receive bank transfers that are free into its own account. He had the AI go through 12 months of Revolut and Stripe charges.
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.