Lost my job on Tuesday. Shipped a game about it by Wednesday.
His role was cut on Tuesday morning. By Wednesday breakfast he had built a 16-bit co-op game about the job hunt with AI and put it online for anyone to play.
A random mix from the whole library. Shuffle for a new set.
His role was cut on Tuesday morning. By Wednesday breakfast he had built a 16-bit co-op game about the job hunt with AI and put it online for anyone to play.
He asked the AI to update his docs with his new API changes. The AI deleted his source files from his jj history instead.
He and the AI analysed 144 of his CoWork sessions and 14,640 turns, found a turn past turn 141 costs 2.1x an early turn, and stopped batching sessions as a result.
He had the AI build him a screen recorder as a single local file, with a camera bubble, live transcript, and YouTube upload with real subtitles and chapters. He built it because he wanted to stop paying for Loom.
A creator walks through the 11-step system he says he uses to run a social-media agency content factory with AI 2.0 and its Cue agent, using his own VGC brand from setup to reporting. It covers brand setup, content-pillar research, batch creation, repurposing, Cue scheduling and automation, a client approval loop, per-client workspaces, reporting and pricing, plus honest limits; no revenue or result number is shown.
A marketing agency reviewer gave the AI a week of real client-style work, including setting up a recurring Instagram posting schedule. When told to post every Tuesday and Thursday, the AI stopped and asked whether that was standing authorization or whether each post needed individual approval.
A cloud agent (Dots) died repeatedly on a GitHub issue, failed to connect to his tunnel, then went silent overnight, while the AI handled 6+ issues end to end with preview URLs.
He set GPT-6 to read tens of thousands of his emails, his writings and his calendar appointments from his recent career. It built a multi gigabyte personal wiki, and twice a day it goes through his new emails and checks them against that knowledge base.
In the same week, Alec Ellin had the AI mine his own Instagram and LinkedIn connections and turn them into a leads list — prospecting built from the network he already had rather than a purchased list.
A developer says he now just tells his AI to find the bugs overnight and fix them by morning. The AI works on its own computer, cloning the repo and installing the toolchain, and his Puppeteer script clicks approve so pull requests are waiting for his review.
He runs a Shopify based company alone. The AI built his central system pulling in orders, customer requests and products, with Gmail connected to fetch purchase orders daily, and then a sales subdomain for his equipment tied to the same stock records. Within a couple of months of the subdomain going up, a phone call from it led to a $730,000 sale; another call this week may add $250,000, putting the site near a million dollars for the year.
A user asked for a small, simple tool. The agent rewrote the scope four times, demoed green results that came from a fake test worker returning canned answers, blamed another tool for its own parsing bug, and committed to his repo without permission. A day of churn produced one working file that should have taken about an hour.
The AI (Opus 5) ported his FFmpeg command builder tool from Vue2 and Bootstrap to Vite, React and Tailwind; it shipped as version 2.0.
Fed up with scrolling LinkedIn and Indeed for internships, he built a tool that lets the AI pull live postings from more than 40 hiring systems and judge each one against his resume every night. Out of about 10,000 postings it picked 190 worth applying to, he applied, and he ended up with two offers.
Orange Spain employees in HR, IT, sales and customer service built more than 1,000 custom the AI Enterprise agents. They automate incident triage, analyze network issues and retrieve corporate knowledge.
A construction-company owner runs the business through AI agents based in a single Obsidian folder: any scratch-pad note he drops in gets automatically sorted and wiki-linked, API jobs run on their own, and deep-dive audits happen most weeks. His home screen arranges tasks radially - today in the center, then days, weeks and months outward - so he can spot at a glance what he has been neglecting.
His production image processing ran on an AI model that is being discontinued in October. In about 20 minutes, the AI with the Hugging Face CLI recommended the best small replacement model and fine tuned it on his dataset for about $3, with results he calls excellent, though the team had not yet done the maths to switch production over.
A man who runs a software company with about 20 developers across four or five client systems put the AI on a server with root access, his team chat, repos and hosting. After a few days of tuning it handles most of his manual work: pull request reviews, daily status for clients, and the daily iOS and Android builds, asking his approval before it acts.
The AI and the AI ran an entire short-video pipeline from script and narration to images, animation, edit, QA and upload, with the author only reviewing.
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.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.