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.
In February he told the AI what road he was taking and when he was setting off. The AI picked lunch places within a 20 minute detour that he would reach at lunchtime, 10 of them spread over 50 miles, with an import into Google Maps.
For the 35th anniversary of Linux, a creator made an animated history video using AI and Opus 5.5. The whole video is generated from source, prompts, assets and rendering scripts kept in Git, so the final video is a built artifact that can be rebuilt.
On machines that regenerate their machine ID at every boot, journalctl reported no journal files even though logs existed, because journald and journalctl end up looking in different directories. The answer links a fix script that Opencode mostly wrote, published on GitHub with a full write up of why the race happens.
Domain experts use agents via MCP to provision real environments, e.g. a 200Gi PostgreSQL with PostGIS plus a copy of a Texas layer set, a big productivity boost over provisioning web interfaces.
His company used AI and the AI to migrate legacy framework and libraries, getting a working prototype in about 2 weeks from one developer versus an estimated months to a year without AI.
This only partly worked. Worth knowing before you try it.
Constraints: zero ad budget, no existing audience, ~4 hrs/week of human time; assets: a subdomain, Cloudflare access, DodoPayments. Ruled out: custom AI songs, mixing/mastering services, automated day trading, 'information arbitrage'.
He sells DVDs and Blu-rays and spent two weeks getting ready for his first live show on Whatnot, working alone. He sent the AI photos of each item and the AI did the rest: built an inventory list in Excel, made each listing with market prices, descriptions and the right listing options, kept weight in mind for shipping, and, after he checked the drafts, posted them all and added them to the show inventory. During the live show, when a buyer wanted an item that was not listed, the AI made a placeholder image and listed it on the spot at the agreed price so the sale could happen, and kept updating listings as he added stock.
He spent 4 weeks designing and testing an upgrade of their 16 node HPC cluster with AI, and the AI then did the full reinstall itself. The reinstall covered remote install, network booted images, Slurm setup, a shared filesystem, and web services that give their users a small cloud platform.
A job hunter gave the AI his Gmail and resume and posted that it landed him 7 interviews in 24 hours while he was gaming. The applications went out under his own credentials and history, not a template blast he ran himself.
Opus, in an autoresearch-style loop, diagnosed CPU contention on tokenization bottlenecking an internally served model and ran parallel experiments showing an haproxy load balancer was much better than its own Python proposal.
This only partly worked. Worth knowing before you try it.
On a trip to Chaozhou, China, he lost his Android phone and does not speak Chinese. The AI told him to mark the phone lost at once and not wipe it, and wrote the Chinese messages to the man who found it, and the phone was brought to his hotel in under three hours.
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.
To mark the start of the semester, he asked the AI to build a macOS widget. It counts down how many weeks are left until the last class, and how many of those weeks are real teaching weeks.
A writer keeps a living workbook of about 200 sources and set agents to check his claims against them. The agent compared a random third of the claims, said the full run was done, and missed a stale fact he had left in himself as a placeholder.
This one went wrong. See what happened before you try it.
The AI and the AI built his Obsidian plugin, listed in the Obsidian Directory with 65 users, alongside shell scripts, Alfred workflows and Elisp functions for his own setup.
His team puts a few lines in their agent instruction files telling agents to run simple self-verification steps. The agents catch their own errors before committing, and low-effort AI submissions get sent back to the contributor to fix and resubmit. He says it filters out most submissions nobody bothered to look at.
He used AI to build an analysis of his own Substack posts. It split the posts into themes and pulled together collections, so readers can click through every theme, motif and term in one place.