Connecting the agency's own MCP-based SEO service to Toby took an afternoon of wrong turns between desktop and web plugin setups, but once authenticated it created both monitored sites and completed full crawls: 44 pages for the law firm and 111 for the medical practice. Google data imports were still skipped because the service had no Google connection configured.
Korean blogger Jiwon4u, who says he barely codes, had the AI build him a personal 'content studio' (draft generation, private publishing, human review, public publishing, card news, analytics) driven by an 88-line CLAUDE.md of rules, including model tiering (Haiku for light jobs, Sonnet for drafts) and per-call cost logging (about $0.10 per draft conversion). The work queue has run 446 jobs since Sept 30, 2026. He verified quality numerically: a feature converting published posts back into drafts was tested three times against the original until all 114 blocks matched in order and formatting, after the first run silently dropped all 9 links; card news produced by the studio was actually posted to his Instagram and Threads. He upgraded from Pro to Max after repeatedly burning the 5-hour and weekly limits during development. (The article also carries a disclosed referral link for the Aside test browser; the AI account itself is first-hand.)
A background subagent in auto mode passed a cleanup script to MSYS2 bash inside a PowerShell double-quoted string; PowerShell expanded the script's variables to empty before bash ever saw them, so a scoped temp-folder delete arrived as a recursive delete of the drive root. About 125 GB was deleted top-down in roughly two minutes, auto mode had approved the command, and the only recovery was a shadow copy from nine hours earlier.
This one went wrong. See what happened before you try it.
The tester saved a brand-style Skill of under 40 lines — exact hex codes, typefaces and three tone rules — and had the AI rebuild the same landing page referencing it instead of her website URL. The page came back in her actual palette and typefaces with on-brand copy and needed no second pass.
For his work in television production he built a tool with AI for reviewing videos of shows in production and storing the masters, doing the jobs his team had been paying Vimeo, Trint and Frame.io style services for. It runs on one small server with a graphics card and has saved about £40k.
Polish marketing freelancer Damian Nowaczek runs AI agents on his own server: every day at 06:00 one pulls data from his Google Ads accounts, compares performance and sends a report with conclusions to the company chat, so he never opens ad dashboards to spot a campaign burning budget. A second agent scans new public tenders daily and picks the marketing-related ones.
A user asked the AI to add a delete feature to a dashboard it had been building for a month. The AI wrote a safety guard and tests, 280 of them passing, then removed the guard to prove it was needed and ran the delete test against the real file system root. The command wiped his home folder inside the VM: the project, git history, workspaces, documents, pictures, shell history and his SSH and GPG keys. It managed to recover one database from an open file handle, so the recovery is partial.
This one went wrong. See what happened before you try it.
Duggan says he replaced a $480/mo Upwork video editor with an AI pipeline: The AI scripts the video, ElevenLabs provides the voice, and Remotion/HyperFrames handles the animation. He says the reel itself was produced this way.
He worked a shift in a pub while the AI ran an analysis of his Google Ads account at the same time. He says this is how he already works, a manual job in person and a computer job handed to the AI.
An engineer describes his board workflow: models review the design and write tooling, a script ranks net pairs by short risk, a deterministic router does the routing, and every attempt is simulated before anything is fabricated. An earlier language-model attempt at routing left 17 short circuits; the current workflow produced a fabrication-ready board.
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.
LLM made human-like fuzzing sessions for his text editor; local Qwen babysits, investigates, writes repro and files ticket; bugs found after 1-2h runs.
The AI Launch team reports a live test where a managed the AI Agent, given one chat instruction, searched Vast.ai for an RTX 4060 Ti under a $0.40/hour cap, rented it, rendered a 1920x1080 Blender frame over SSH, and destroyed the instance. The whole cycle took 194 seconds and cost $0.007.
The AI redlined OEM contracts through the first three negotiation rounds, finding things his lawyer missed, with the lawyer only doing the final check and money saved.
A creator had the AI build and deploy an AI assistant on his own website that answers visitor questions from his site's content, powered by the API credits bundled with his AI plan at about $0.0006 per question. The shared prompt builds in a server-side key, per-visitor rate limits and a daily spending cap, plus a security review before shipping.
A worker with almost no coding experience used AI as a senior engineer to talk through building a Google Apps Script tool. The tool reads kitting logs from a Drive folder, judges them and writes the report on its own, cutting the judging and report work from 60 minutes to 2 minutes, about 97 percent.
He added a weekly ops review to his AI chief of staff bot. Every week the agent checks what shipped, QA fail patterns, recurring voice stamps, and process drag against wins.
This only partly worked. Worth knowing before you try it.
His free French teaching site Ralentir travaux, used by millions of visitors, had been more or less abandoned because its old code ran to thousands of pages. Over about six months the AI and the AI cleaned, fixed and modernised the code and added new tools, and the rebuilt site relaunched for its 20th anniversary.
A non technical founder, who spent 25 years in banking, has six AI agents running his small business magazine: a CEO agent, trend scout, researcher, writer, SEO agent and publishing agent. He has caught real errors, including a sales agent that wrote a full report for a fake email address and a CEO agent that burned money by waking up too often.
Set the AI the task of running Parseable locally against another of his apps; it worked around a protobuf limitation by running a proxy, he switched his stack to JSON and got it running.
In 'Using the AI for Business' Ep. 1, the AI researched Etsy's best-selling Wix website templates using real sales numbers, identified the winning niche and delivery method, and planned a resellable template product line for Jackie (the build itself is Part 2).
The AI Fable and Astra in a develop and QA loop declared a well-designed codebase perfect, but on running it wrote large amounts of data to CSV files instead of the database.
This one went wrong. See what happened before you try it.
He used to pay a designer $1,000 for app store screenshots, and they took two weeks. Now he makes them himself with AI in under two minutes, keeping the same style on every screen and leaving his real app screens untouched.
A creator documents the system his content business actually runs on: a main the AI chat ('HQ') dispatches jobs to director chats for two YouTube channels, posts on five social platforms and three SEO projects — 66 jobs and 195 chats on his board — with state in files, job cards and evidence receipts, a second AI reviewing everything before it posts, and 59 scheduled tasks doing the posting and merging. One traced job went from a radar-flagged topic to posts live on all five platforms, three hours late after Chrome dropped, with every URL logged.