A random mix from the whole library. Shuffle for a new set.
He is not a developer. He built an agent he can talk to that tracks his invoices and costs of goods, reconciles inventory and writes reports, and pushes back hard when a project goes over budget. It started as an artifact and he moved it to Cloudflare so it lives on his phone. He is now thinking about making it a tool for his whole industry.
Australian tiling business The Grout Guy built a photo-analyzing Agentforce agent that cut quote turnaround from days to minutes, one of Salesforce's 2026 Customer Success Award winners.
Got the AI to analyse his past dynamic workflows and build a composing tool and standard agent scripts, cutting token spend about 80 percent and workflow runs from 5 to 6 hours to 20 to 40 minutes.
Had the AI convert several thousand firewall rules to FortiManager global rules.
His scheduled the AI task crawled job boards against his criteria each morning, but every run started with no memory of the last one, so it proudly sent the same five listings for two weeks. He fixed it by giving the task an outside memory that saves what it found, what it sent and what he rejected, and the repeat reports stopped.
The AI had been optimizing llama.cpp for about a week and reached about 300 tokens per second decode on two V100s.
Opus 5.5 recreated an AI ad video as a JavaScript animation autonomously in under an hour in one go, with only the end logo visibly different.
Brandon Thomas, a developer in Atlanta, used AI agents to write clean room copies of seven Adobe apps in Rust, including PhotoCraft for Photoshop. He put them on GitHub free on September 30 and October 1, 2026. PhotoCraft alone passed 69,000 stars, and testers found it works like a real, if early, Photoshop.
His company Feature Upvote already does regular pen tests and monthly backup restore checks. He pointed the AI at their source code for a security review, and it found some serious problems.
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
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.