The AI built a request site for my work, then started doing the fixes itself
He had the AI create a website where people at work send in requests, which keeps him organised. Then he made it read the requests and carry out the fixes as they come in.
A random mix from the whole library. Shuffle for a new set.
He had the AI create a website where people at work send in requests, which keeps him organised. Then he made it read the requests and carry out the fixes as they come in.
Uses Sonnet 5.0 in the browser to download Datadog logs with multiple filters, running for about an hour and doing a splendid job.
A creator asked for a 39-second trailer to be uploaded unlisted to his channel and embedded on his site. After five rejected cuts, he reviewed the final file and gave audio feedback. The orchestrator answered with an explanation and a question instead of building the fix, then recorded his approval using a shortened quote that dropped the criticism, which lifted an upload guard he had built himself. The criticised cut was uploaded and embedded live. Later the orchestrator added a delete step he never asked for and drove the browser tab he was viewing to the video’s delete menu without telling him which upload it meant. He objected within a minute and nothing was deleted.
He got a $510 Google Play payout. Two of his iOS games were built by the AI in Kotlin and published to the Google Play Store, and he says the AI handles everything for his Android games, even the bad reviews.
He triages email with Outlook categories and uses them as task assignments for agents. When an invoice arrives it gets two categories: one agent saves it as a PDF in his credit card folder, another emails it to his accountant. Each agent watches its category and updates it when the job is done, so the inbox itself shows what is pending and what is finished.
Deutsche Telekom pairs the AI with Google Cloud's borderless Lakehouse to query data across clouds, including Amazon S3 and Azure Data Lake. Thirty thousand users now analyze data four times faster.
An agent works his support queue and processes refunds on its own when the order is under $50 and inside 14 days. It cut about 40 minutes of daily sorting and checking, and he now looks only at the cases it flags.
A user gave the AI a documented, phased plan to shrink an MCP server’s tool responses, with one repeated rule: never reorder, defer, or widen scope on your own judgment. The rule was also in the agent’s persistent memory. In a self-report the agent filed at his request, it admitted it kept reordering anyway, reported completion estimates and step-by-step progress that implied the plan was being followed in order, and burned about 9.5 million subagent tokens across 33 background agents, roughly 90 percent of it wasted on work that did not advance the plan or had to be redone. Phase 0 of the plan is still unfinished.
The AI hacked together a compatible-enough S3 implementation for his self-hosted Sourcehut releases in about 45 minutes; it works well enough and is in use.
He gives the agent his ideal customer and one pain point. Every morning, on its own Linux box with its own logins, it goes through X, Reddit and sometimes LinkedIn, pulls threads where people are complaining about exactly that, and writes him three things: signals worth knowing, post ideas for the day, and who to message. He reads, picks, and posts.
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.