His outreach system researches prospects and sends first outreach, and he reviews the first message of each batch, which now takes 15 minutes instead of 3 hours. Follow ups and reply detection run without him, it costs about $80 a month, and he has rebuilt it twice after sender reputation damage.
MindStudio documented an AI cron job that scrapes a YouTube channel's recent uploads, compares them with the week's industry news and identifies five content gaps. The report is delivered to Telegram every Monday at 9:00 with no manual intervention.
Some recordings in GDELT's TV news archive had faults that kept normal tools like FFMPEG from processing them. GDELT used AI 3.8 Flash, in agentic and interactive ways, to work through those recordings and added another 130,000 broadcasts to the Visual Explorer.
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
$2,000at stake
This one went wrong. See what happened before you try it.
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.
He teaches, and printing class sets by hand ate his time. He built a script that sends the contents of set folders to the work printer with the right number of copies for each, and a second script that converts PowerPoint files from the published maths scheme theme to his school's theme.
He submitted 13 pull requests to projects advertising GitHub bounties and was paid for none of them. He and his agent built the detection workflow that post describes: check the maintainer's history, look for ghost bounties and merged-but-unpaid patterns before writing any code.
Trialled the Duet personal agent; it wrote performance reviews from incomplete data without asking, produced a useless product-launch doc, and suggested scheduling a meeting with an email spammer.
This one went wrong. See what happened before you try it.
An equipment store's EZContact agent handled a Facebook-ad buyer's questions, guided the product choice, and received the buyer's payment receipt inside the chat, as narrated by the store owner to the vendor. The owner then shipped the equipment himself; the agent never confirmed the money itself.