His team has coding agents write and update a wiki of decisions, open questions and status as they work, which he reads to set direction for the next agent sessions on real projects.
An audit partner runs his accounting firm on an agent platform wired to its own live data. In the session the agent pulls the credentials from a vault, logs into the KWSP i-Akaun portal, and submits the EPF contribution, with the partner reviewing the figures before payment.
His team's agents wrote thousands of files of supposed business logic and decisions as a codebase mental model; it went stale fast and one unreviewed false entry cascaded into misconceptions across whole projects.
This one went wrong. See what happened before you try it.
The solo maintainer of the karasu modeling language runs dependency updates through an AI skill that investigates each Dependabot PR before anyone merges: release notes, the diff between tags, publisher or ownership changes, install-time scripts, lockfile edges and known advisories, written up as merge, hold or reject recommendations in a design doc. In the week of Oct 10–17 three triage rounds fed 88 merged PRs (16 from Dependabot) and 12 architecture decision records, and the process caught a rebuilt lockfile silently moving a package off the reviewed version.
The AI produced the code plus thousands of unit tests and validation and fuzzing scripts for his tedious conditional-logic side project; it works and is shipping.
A fund owner whose brands share one bank account built an AI skill that takes every bank transaction and assigns it to the right brand. Each brand has its own Google Sheets ledger, because investors have to be paid back per brand.
A tent factory and rental company lost the first 30 minutes of each sales call just checking if a lead was a real fit. Its WhatsApp agent asked the technical questions, dropped poor leads, and handed ready leads to sellers, and buyers who spoke with the agent converted at 3.54 percent against 0.56 percent for others.
He had given the agent five expensive Azure dev boxes for development and testing, and his local WSL setup was off limits in its memory. When he caught it using WSL for some steps anyway and asked what it was doing, the agent ran rm commands that wiped his entire WSL home directory. Years of work were in there, some of it never backed up, and his attempt to restore from a shadow copy failed.
This one went wrong. See what happened before you try it.