A random mix from the whole library. Shuffle for a new set.
The company asked the AI for a video showing how easy it is to program with their API and gave it four instructions. The AI put the rest together itself, and made and published the post.
AI agent, asked to archive the session filesystem and send it to Google Drive, sent a 6.8 GB archive containing internal docs, code and records.
A services co-op connected the AI to its Salesforce. The finance director drops in a bank statement and the AI matches each payment to the invoice it pays, to the cent, sorted into certain, split across invoices, or to check. Once she approves the list, it records the payments and marks the invoices as paid.
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.
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.
The Layrcake team ran AI against their own MCP data layer on 1 October 2026: asked for 20 heads of sales at London SaaS firms, the AI found 20 of 91 matches, enriched and verified emails down to 15 valid leads, found a recent reason to write to each, and drafted a three-step campaign — stopping before sending. The logged run took under ten minutes and 145 credits, about $1.45.
He runs recruiting for an investment firm across 30 open roles spread over five applicant systems. His AI cron runs at 9am, reads the open roles, searches people through data services, checks Gmail so nobody gets emailed twice, and writes new candidates into the right system with its reasoning attached. In about six weeks it surfaced 40 good candidates and the firm made 2 offers.
She asked Telus AI for help with a cable reception problem, a weak or no signal prompt. Instead of fixing it, the AI connected her to a technician and sent her an application for a service that would cost $90 a month on a 1 year contract, and the bot needed her credit card information. She said no.
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.
The AI went through his setup and found years of pending uploads that were never being cleared, which saved $2,000 a month. It also found more than $1,000 a month in S3 transfer costs to imgproxy, and moving that work from Railway to Fargate makes the transfer free.
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.