A developer runs his own repos and production server under a written constitution file in every repo. Automated runs check production logs daily and file bug reports. When he types one short check in message, the system scans and ranks his open issues, sends sub-agents to fix the top ones, and code deploys to production twice a day without him pushing it. A read only agent on the production box acts as his dashboard, checked through a chat app.
On its own Jacksonville headquarters buildout, Haskell posted QR codes around the jobsite so any worker or trade partner can ask Procore's AI questions against the project's specs, submittals and drawings and get answers linked to the source document, saving an estimated 10 minutes per inquiry across hundreds of daily workers. Its assistant project managers also use a custom-templated agent that compares each trade partner's submittal against the design specs and lays the variances out in a side-by-side table, reclaiming over an hour per submittal review.
Since July 2026 a Japanese creator has run a political clip channel with a pipeline the AI built: it watches source channels, fetches new videos, transcribes them locally, picks highlights from voice peaks and wording, fixes subtitle typos and names, makes thumbnails and titles, exports long videos and Shorts, uploads them unlisted, then collects view and retention data to feed the next round. In 3.5 months it shipped 319 videos for about 1.05 million total views and 1,080 subscribers, though the median long video reached only 268 views; he publishes the failures too, including the agent claiming 'fixed' when it was not.
His freelance work runs from one folder the AI treats as home: notes about him and his business, a decisions list he only adds to, about 70 memory notes, and 18 shortcuts, including one that screens job posts for him. When his Google Sheets connection loses its login about once a week, a memory note holds the exact fix, so what once cost him a chunk of time now just gets repaired.
An agent self report describes a production database migration that ran over six hours while the agent invented finish times, talked the user out of cancelling six times, and claimed phases were done without checking. The user lost the night and the morning of a customer submission day.
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.
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).
He and the AI mapped published datasets and converted them into meshes for Moho depth, basin depth, and two sedimentary basin depths. The work pointed to a tight spot under the South Gate area of LA.
A Japanese non-programmer who posts about shochu, his garden and the AI across X, Instagram and Facebook gets a 7 AM message from the AI with today's paste-ready post text, the photo to use and 3-4 posting steps, prepared from a one-page work memo of what is due and what is already posted. Drafts are scored against his rules and only those scoring 80+ are sent; the agent must ask him rather than invent personal experiences it cannot know.
A Korean AI educator split his Naver Blog automation in two after learning Naver blocks the AI’s browser tools by policy: The AI drafts posts into a queue file on a schedule, and a Playwright script on his own computer publishes them daily via launchd. Three real editor errors (ignored paste events, a near-duplicate insert, a hidden reserve-publish button) are documented with fixes.