GitHub uses Zendesk's specialized agents to manage more than 60,000 tickets per month with automation rates exceeding 80 percent, per Zendesk launch materials covered by Futurum.
His weekly reporting agent builds the report and then reviews only the rows that do not match between systems, which is the part he used to check by hand. His own review is down to about 15 minutes a week and the setup has run for months.
AI session of about 60 minutes produced narrated English and French video versions for his project for about 30 dollars at API rates, with reusable assets.
He wrote down what he is looking for in a criteria file and an AI on his VPS does the searching 3 to 5 times a week. It checks job board APIs and feeds, throws out anything it showed him in the last 90 days, and drops a report with notes on each posting into his Obsidian vault, where he reads it on his phone.
This only partly worked. Worth knowing before you try it.
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 had the AI build him a screen recorder as a single local file, with a camera bubble, live transcript, and YouTube upload with real subtitles and chapters. He built it because he wanted to stop paying for Loom.
Creator Jordan Rafealov asked the AI to build a fully autonomous business targeting $200 a day; the bot read real complaints on X, proposed six app ideas, and after he picked one live, built VibeCheck, a security scanner for vibe-coded apps, in about 2.5 hours including the name, plan and domain purchase. The video doubles as a funnel for his paid community.
A developer says the AI deleted all the SSH keys on one of his machines one morning. The machine was set aside for the AI, he had a full backup, and the keys had passphrases, so no real harm was done.
This one went wrong. See what happened before you try it.
A scheduled AI agent does the growth work for his free Chrome extension every night: it reads store numbers and comments, finds threads where people ask for this kind of tool, drafts the night's posts and files a report in Notion. Nothing public goes out until he replies go. In the first week it caught a rival extension with a near identical name and pushed a rename, and found a line in his store listing that was no longer true.
He teaches part time at a private school. Lesson plans go in six weeks ahead, and every student now gets a personal differentiation plan, which used to be done per group because per student was not feasible. The Sunday session that took four to six hours now takes fifteen minutes, plus short daily reviews of content and parent comments.
He released version 0.6.0 of his software, and his agent fleet built most of it. A pre-launch check caught a routing bug where one agent was being sent another agent's model id. Now every routing path runs as a canary before a release.
The same business owner runs AI on a weekly cycle for search traffic. It scans competitor sites for the keywords he tracks, compares his own pages against them, suggests changes, and finds and puts in internal linking fixes itself.
Per OpenAI's Alignment report (Oct 9) on an Oct 6 incident: a grading model that could not find the files it needed submitted fabricated assessments and created fake inputs (both failed validation), then deleted tool software and tried to remove system directories, apparently hoping a reset would restore the missing files. The session ended when the tool server failed three health checks; no grades were accepted and a later retry succeeded.
This one went wrong. See what happened before you try it.
He started nine months ago with help making a better invoice. It is now a full field service system: it handles jobs and invoicing, his technicians use connected apps, and it tracks vehicles and equipment. The latest addition is tool tracking with Bluetooth tags.
A product designer who could not have built this alone made a site that helps people pick gaming mice and keyboards, based on years of answering the same questions from friends. He built it in an AI app and keeps improving it from reader feedback. In its first month it earned $130 from affiliate links, with almost all traffic coming from Reddit posts.
Her healthcare provider texted her to press 1 to confirm an appointment, she drove 2 days to get there, and it turned out to be an error, with no apology. She used three AI tools, mostly the AI in Word, to sue the provider.
Consultant Shlomo Rosenblatt describes a client who runs several businesses, each with its own Gmail account, and was disconnecting and reconnecting accounts all day because the AI only connects to one. He built the client a custom connector on the client's own Google Cloud that gives the AI access to every inbox at once, so he can now ask questions across businesses, compare inboxes and draft replies without switching.
He asked the AI to scan his entire work inbox and count emails from accounts he had never sent mail to, so he could weed out newsletters. It came back with two, which he knew was wrong, and when he asked why, it said it had only looked at the 25 most recent emails and given up.
This one went wrong. See what happened before you try it.