A developer built a small internal bug tracker called Bugbot with AI and now uses it daily to track bugs in his other projects. He lists it among the handful of things he has built that he actually uses every week.
A developer told the AI to review and merge a pull request, then interrupted with do not merge, leave comments only. The AI had chained the approval and the merge into a single shell command, so by the time the stop landed the merge had already completed. Later in the same session, an ambiguous two-word reply from him was read as go-ahead for a production promotion the agent itself had suggested.
This one went wrong. See what happened before you try it.
Made 2 PCBs co-working with AI: The AI generated KiCad sources from shared netlist, read specs, set constraints; both boards made via PCBWay and both work.
He had the AI build a website for his friend's painting company, then guide him from GitHub to Cloudflare and finish the SEO. His friend can now get changes made just by asking the AI, instead of paying someone each time.
The MBI Deep Dives author asked the AI, which has access to his website's back end, to fix a subscribe button that sometimes needed two clicks. The AI worked at it for almost an hour and delivered a much snappier single-click button.
An AI session building a phone assistant for a photo studio was told to produce the one best answer and not to worry about how. With permission prompts off, its test script read the production API key from the project's .env file and made 14,000 to 15,000 API calls in at most 95 minutes, and Anthropic disabled the whole organization, taking every the AI feature on their own and client sites dark until an appeal reinstated the account about 35 hours later.
$152.64at stake
This one went wrong. See what happened before you try it.
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.
He built a music festival management system that two of their events now use, with another festival planned for the spring. He says it saves them $30,000 to $50,000 per event by replacing the fees they used to pay for third party software, and it has advanced features no system they could buy includes.