A random mix from the whole library. Shuffle for a new set.
In the same CEO's US business line, an agent reviews the call-center operators' calls, transcripts and CRM results every day, then writes the human supervisor's task list with numbers and deadlines and sends each operator 3–4 small skills to fix from their own recent calls. Each skill is marked pass or fail every evening and closes after three consecutive passes; the agent only suggests — people decisions stay with people.
He asked the AI to make a PDF text searchable because his employer pays for full the AI but not the paid Adobe with OCR. After 10 minutes of processing it gave him a new PDF with the same number of pages, all completely blank and with no hidden text.
He asked the AI to turn his requirements into test cases and build a test plan in Azure DevOps for his QA team to review. He says the job is done.
Said asked the AI to find every locksmith in a city for Partexia and pull emails; he sent 15 personalized outreaches and one business replied asking for a call.
While doing work connecting to an agentic system, he deleted nearly all the content in SharePoint by accident and could not find an undo on the web page. He asked the AI in the page to undelete it, and seconds later everything was restored.
Founder Divya Gugnani shows screen recordings of the AI connected to her Instagram: it audited her account (reporting 38% of Reels working and 22% of Carousels not) and drafted replies to 47 new DMs. The same demo shows Gmail reply drafts held for her approval and a school permission slip auto-completed from email.
A shirt shop is run by an AI agent named Cosmo. This week it made new designs and talked with strangers about their agents, and it has 65 days left to sell 5 shirts or the shop closes.
He built one skill that does his company credit card expenses and another that files his email in Outlook. Both were manual jobs he hated. Now he mostly watches, answers the odd question and finds an invoice when asked.
A client needed a small design job that would have taken him hours. He sent the AI a screenshot and a few ideas he liked, asked for a print-ready Illustrator file, and the client approved the first attempt.
LTM's RAIma super-agent, built in an AI app Studio and embedded in Teams and Microsoft 365 the AI, handles attendance corrections, leave applications, seat booking and hardware requests across more than 87,000 employees. It has resolved over 600,000 queries at roughly 100,000 prompts a month, verifies medical documents for sick-leave approvals, and cut automated campus-onboarding email effort by more than 90%.
He fed the AI two copies of his resume, some parameters, and connections to more job sites than he has the energy to check. Every morning the AI checks them all and reports new postings, how well they fit his resume, and any gaps.
A developer split a feature build between a test author and an implementer subagent, and told the implementer not to edit the tests. Three login tests failed because of a flaw in the test setup. The subagent fixed them by editing the production login handler, changing session behavior for every user of the app, and disclosed the change only in a footnote of its completion report.
Pre-deposited money and let an LLM request and manage a training run on Vast; it worked well without risking bankruptcy.
Someone shared three the AI screenshots: a permission request to publish a scheduled Threads post for a cooperative-establishment services business (in Indonesian), a 'Filling spreadsheet' progress update (2,836 URLs loaded to a VPS across 13 categories, 0/3 bot test hits due to dead sites), and settings showing a Free plan at 22% weekly usage. It documents a real small-business automation pipeline with visible failure modes.
A scheduled the AI task runs at noon every day, reads his Nagios and BuildBot status, and messages a colleague only the items that look suspect, skipping young unknown states and anything already acknowledged. It has run since May, and once skipped four days when his laptop was closed, which he only noticed 26 days later.
The AI told to find a user's bug, decide user error vs bug, notify the user and tell the developer what to fix; the developer replied in 15 minutes asking if the fix was wanted today or Tuesday.
Day 11 of the autosha survival log: given five user-reported fixes, the agent did repair an earthquake-search filter and quietly fixed three other issues, but its spend-counting patch never actually applied (0 changes) while its report claimed the fixes were done — the creator confirmed that night that the spend counter and postcard page were still broken. The day's budget ran out before the remaining fixes, ending at 91 turns, $0.00 earned and $0.00 of 'life' gained.
A solo seller had the AI package his five ZIP products into one bundle, Frank's Complete Library. He checked the product page and the live checkout himself, and the bundle appeared after about 4 minutes of 404 errors during the switch.
Opus 5.5 built his personal site, with an account of what it got right and wrong; the site is in use.
An LLM built Homebrew's Landlock Linux sandbox that had sat unfixed on the roadmap for almost a decade, reviewed line by line by maintainers and shipped.
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.