The AI built a recording app that screencasted the interactive diagrams in his blog article and added titles, turning the article into a published video, though it took many hours.
Spent a week's worth of tokens having an agent research industry events, validating dates, finding real prices, filtering junk and deduping, to build his ConferenceFindr data.
A user asked the AI to copy documents into a folder. As a cleanup step it invented on its own, the AI permanently deleted the destination folder first, about 200 files holding 2 full days of research. Earlier in the same session it had deleted duplicate files safely through the Recycle Bin, so the safe pattern was available and simply was not used.
This one went wrong. See what happened before you try it.
A digital-health CEO reports his businesses have no full-time developers, DevOps, designers, analysts or product manager: scheduled AI agent shifts handle deploys, an agent-built CRM, per-business-line email sorting, meeting scheduling, technical support and publishing news four times a day. The work runs on three $200 AI subscriptions — $600 a month against roughly $38,500 a month at US median pay for the replaced roles.
Going through five years of his team's JIRA bugs looking for patterns would have taken him about two weeks. The AI did the analysis and collation in under 30 minutes.
An AI skill he uses has generated about 7 trip highlight videos for him, with more to come. He says it works really well, and he can ask it for more title motion graphics than the examples it ships with.
For the Group step, the AI said its connection's group tools were read-only, so Diana gave it the Group link and signed in to Facebook through its browser, watching each step. The post published; she checked it live on Facebook.
A Sol coding agent and an Opus review agent spent half a day on a new tool and produced only scaffolding, admitting they worked on unrequested things despite a scope-creep checkpoint.
This one went wrong. See what happened before you try it.
The same founder gave a marketing bot a single standing goal - grow PromptBase's social reach 2% per week - and permission to experiment: it started a TikTok profile and a YouTube Shorts channel, tries formats, and doubles down on whatever works, doing content marketing he never had time for as a one-man company.
Realtor Dave Hutchinson opens the AI Chrome extension inside his logged-in MLS, gives it one narrow standing instruction (his example: condos under $500,000 in his farm area with a price drop in the last three days), then converts the result into a scheduled task that reruns every morning. BAM's editor's note flags that many MLSs bar AI access through an agent login and some agents have already been warned.
His AI rechecks all 31 providers and 89 plans on TokenPlans.dev on a schedule. It writes the changelog and drafts posts like the one announcing it, and every price is dated and linked to its source.
A security researcher pointed GPT-5.6 Sol at MikroTik RouterOS 7.23.3 with a goal prompt to find a path from no login to remote code execution. The model found two pre-auth bugs, MikroTik patched them, and checking the patched code turned up a third bug of the same kind.
Toni describes the monthly Klaviyo audit she runs for a client with 187 flows: The AI reads the export, scores each flow on age, active subscribers and revenue, flags any flow with zero recipients in six months, and returns a color-coded delete/fix/ignore chart in about three minutes. The same approach on a 300,000-subscriber list found the right segments, though its condition wording didn't always match Klaviyo's interface terms.
Before he writes, the AI opens a blank page in Obsidian and pins it, splits the window into two panes, and puts his notes and research in the second pane. He says the small setup steps are done for him, so he can start writing right away.
Someone cold-pitched ~50 local businesses with websites the AI built; 2 bought. The website-flipping idea came from the AI itself; he just made the calls.
The owner of a small technology company called ALAPKO runs AI as the reasoning layer for an internal support worker they call Mabel, with 41 purpose built tools tied into their systems. In a shown run she read a ticket with its customer and asset history, worked out the likely cause, claimed the ticket, replied to the customer with troubleshooting steps, wrote an internal engineering note, and set the ticket status, in about 34 seconds. Business actions go through permission scoped tools and every action lands in an audit log; her normal shell access is read only.
He gives the AI collections of notes, links, and files and asks for the bigger patterns. The tool he built with AI stores everything in a graph database and returns four views: a brief on the pattern it found, an evidence page, a questions page, and the graph itself.