An agentic harness for Sonnet 3.5 converted a medium-large vue-class-component framework to Vue 3 composition API, rescuing a personal project from software rot.
He is a photographer. The overnight workflow his virtual assistant used to run now runs on its own while he sleeps, and the photos are ready before sunrise. Today he let the virtual assistant go.
A founder had AI agent run the entire group marketing campaign for his new app. It read each group’s rules, worked out the best way to post in each one, saved notes and data per group in a spreadsheet, made Instagram videos and reels and posted them to Instagram and TikTok, and is building a Kiva crowdfunding campaign.
A perpetual the AI thread in his llama.cpp checkout periodically sweeps PRs and research, rebuilds llama.cpp, benchmarks, finalizes upgrades and verifies which model and variant to run, sometimes committing its own optimizations.
A Low Code Studio creator gave the AI a single prompt describing a Compliance Tracker app; the AI designed the data structure, created the SharePoint list with columns and data types, and wrote the YAML for all four screens. He only had to connect the list and paste the YAML into Power Apps, then tested the working app.
He says his business got serious about Power BI reporting about twelve months ago, then three months ago threw it out and replaced it with AI licences. A third party warehouse tidies the data with an MCP on top, and the finance team now builds its own reports quickly instead of waiting on a reporting team.
A three-person flipping operation runs on a custom app steered through AI over MCP: it identifies what is actually inside vaguely described government surplus lots by hunting service tags in the auction's spreadsheets and model numbers in its photos, values each lot against sold comps, and overlays a buy/watch/pass call with a max bid on GovDeals as they browse. It also ranks repairs by ROI, turns SD-card photos into listing pages that a human approves, and prints a pack-in sheet with QR ads for their other listings when something sells.
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.