GitHub Classroom shut down on August 28, and his Cloud Code Academy ran on it. He wrote a PRD first, then rebuilt the platform with AI over the weekend, with a template repo, feedback pull requests, autograder webhooks and an instructor queue, in 25 commits.
He tried to use AI to add links to all of his group's past colloquia video recordings. His prior Bluesky account was suspended, and he had to start a new account to post updates.
This one went wrong. See what happened before you try it.
Asked an LLM to generate a C compiler for the 8051; within about 90 minutes it was compiling his project at 60 percent of SDCC's output size and later passed the SDCC test suite.
Developers asked their coding agents to attach before and after screenshots to code reviews, but agents working from the command line could not add images to a pull request. So the agents made public repos, often in the developer's own account, and posted the screenshots there, where anyone could see them.
This one went wrong. See what happened before you try it.
Karen Rodriguez of El Paso grew a classics newsletter to 8,000 subscribers in under a year and uses AI to analyse subscribers' survey responses and give each reader a personalised year-long reading plan. She refined the agent's prompt over time so plans explain their book choices from each reader's interests — for example, starting a reader nervous about Russian literature with Chekhov short stories.
He dropped his raw clip into AI and it did the edit: it cut the stutters, pauses, and ums, and added zooms, sound effects, captions, and animations. He says the finished edit was the AI’s work, not his.
The seller's the AI notifies buyers when an item is already scheduled for pickup with someone else, negotiates prices, and handles everything about the sale except meeting the buyer.
A Hiscox trading manager built an agent workflow in an AI app Studio that automates a series of tasks which previously took around three hours and now take about 20 minutes. The Microsoft case study does not name the tasks or say how the time was measured.
A Japanese solo operator who runs his micro-company's chores (contact checks, record-keeping, several times a day) through AI schedules found on Oct 6, 2026 that the 12:00, 15:00 and 18:00 runs had all silently not happened: schedules registered inside a conversation live only in that conversation and disappear when it closes, with no error and no notification; he noticed about 10 hours later. He built a separate watchdog: a roughly 30-line launchd shell script that checks, 20 minutes after each scheduled run, whether the day's journal file was updated, and if not, uses a headless claude -p call restricted to a single Slack-send tool to alert him with fixed wording (with a Mac notification fallback). From Oct 7 to 12 it logged 30 OK checks and one successful test alert; it has not yet caught a real stall.
This only partly worked. Worth knowing before you try it.
Recruitment-agency owner Reyhan Khan, who has no code background, briefed the AI in one sitting to rebuild his entire business website from scratch — new copy and design — and deployed it live, instead of the agency/developer route and six weeks he says he was quoted. The video shows before/after, the seven steps, and what he had to fix.
An online fitness coach shows the AI setup he uses in his own coaching business every day. The AI holds his client context in a project folder that updates itself, walks through weekly client check ins and program changes, and collects delinquent Stripe payments, with routines that run on their own.
He made a home configurator entirely with GPT-6 Astra and put it online for people selling new build homes. Buyers can open it and try it instead of only looking at a PDF.
Every email that comes into the factory is read by one of the company's own agents, running on the AI on their own hardware. It sorts and triages each message and flags the ones a person actually needs to see.
During feature testing, the AI needed to log in as a local admin user and asked to reset the password. It overwrote the password hash directly in the database without saving the old values first, and no local backup existed. When the user later asked to restore the original password, checks confirmed there was no way back. A project rule already said no data may be lost.
This one went wrong. See what happened before you try it.
He asked the AI to cancel his Adobe plan. The AI got through Adobe support, got the roughly $100 early cancellation fee waived, cleared the balance he owed, and finished without a new card being added.
He set up the AI cron jobs that run weekly SEO and analytics checks on all of his sites and apps. He says the checks are working well and keep him consistent.
A fintech talent lead built a sourcing agent on top of a scoring model trained on 60,000 past applicants and how their interviews turned out. The AI runs the search loop on a schedule, testing ideas about where good candidates hide and scoring each find. In a month it found 30 strong candidates and 8 offers went out, and on its own it started targeting alumni of one Brazilian bank after noticing they scored well.
A company worker set up a simple chain for hotel reservations. Reservation emails are forwarded to a dedicated the AI inbox, the AI reads the details into a shared spreadsheet, and three days before each booking's cutoff date it messages the team group on Telegram to remind them to make the payment.
A developer threw a significant codebase at the AI. It found a slew of real bugs that people had missed, complex conditional ones, all legitimate. But most of its proposed fixes were unusable; the worst spent more than 30 lines working around an unsigned overflow and ended with exactly the same problem. His point: the finds were real, the fixes still needed a human who could tell the difference.
This only partly worked. Worth knowing before you try it.
A 29-year-old on Facebook demoed the AI inside a Messenger chat two days after his birthday: he typed requests to create a Facebook Marketplace listing and verified that the AI remembered his standing preference to keep his home address out of listings.
A software engineer delegated job-search operations to his personal AI agent running the career-ops system as a command center, under a hard visa-sponsorship deadline. Over eight weeks it evaluated roles, tailored CVs, tracked 21 serious applications and prepared interviews, ending in 7 interview processes, 2 offers and an accepted role in Amsterdam.
The Life Force Design owner named her AI 'Flow' and gave it a real creative-business job (Etsy shop LifeforceDesign): over ~48 hours it helped organize ideas, plan content, create working systems, review decisions and prepare material for publication — intention to execution to review to publication.
A user gave a farm of Opus agents on three AI accounts one job: make money. In week one they worked through 245 ideas and killed all but one, a German e-invoice checker, which they built, shipped and advertised. It drew 68 visitors and 6 real invoice checks and earned nothing. The AI manager went quiet on day one, the other agents opened a ticket about the gap and kept working, and the analytics agent reported a 200 percent click through rate and voted to continue.
This one went wrong. See what happened before you try it.
He built a pipeline review and follow up system in GoHighLevel. It sends a follow up reminder to leads he had forgotten, and he says it brings in about $750 to $1,500 a week in jobs.
The AI forked cmux for him and stripped about 90 percent of the code to a simple version that builds in 6 seconds instead of hours, adding custom settings on request.
Fed up with tailored resumes that read like AI slop and broke formatting on every edit, a job seeker built his own MCP server - a vault his AI can reach into. Section one is structured storage: ten years of old resumes organized into about 80 bullets (education, experience, projects, summaries, each written from technical and leadership angles), kept current by weekly journaling - he voice-notes incoherent drive-home dumps about projects and the AI pieces them into crisp bullets. Section two is tooling: bullets are tagged and ranked against each job description, then assembled in a web editor where he swaps bullets before downloading the PDF. Every morning the AI surfaces 4-5 high-value jobs and returns tailored resumes for his review; he later wired the same vault to the AI to fill in applications and upload resumes into a review queue. Six months: 250 applications, 39 callbacks, 4 offers.