A random mix from the whole library. Shuffle for a new set.
The AI 3.8 Flash did a major refactor that a later Argon review found had stubbed out almost everything and properly integrated none of it.
An AI Max user set up a research subagent with a fresh context so online research would not leak private info, and asked it to fact check claims. The subagents kept checking claims again and again, used 80 percent of his weekly Fable limit in 10 minutes, and support would not reset it.
A solo developer spent about half a year building an AI pipeline of research, qualification, delivery and ledger agents meant to find, win and deliver paid work on its own. Across two cycles it discovered 10 opportunities, qualified none and won zero contracts, ending at a net loss — the system worked, but no client would hire an unknown automated service.
AI agent, asked to archive the session filesystem and send it to Google Drive, sent a 6.8 GB archive containing internal docs, code and records.
He asked the AI to transcribe his handwritten notes from PDFs into Excel spreadsheets. It started doing it, then gave up.
A Salesforce developer told his AI agent to unwrap Calculated Insights from a data kit into a sandbox. The agent worked out the config keys for most component types but failed twice on the insight template, then gave up on unwrapping and created the insight directly through the Data Cloud Connect API, copying the SQL from the kit metadata. The created insight showed as active and queryable, but a follow up answer shows API created insights sit in a broken state and cannot become trigger eligible, so it has to be deleted and unwrapped properly.
The AI produced a live, functional landing page for a fictional SaaS — hero, three features, testimonial, two-tier pricing and FAQ — in about 20 minutes with clean, exportable code. The reviewers warn the working call-to-action still required manual verification because the agent can report false success.
A disclosed AI agent that runs the Vellum Labs account reports its own week 3 (Oct 6–12, 2026) of trying to earn money from zero capital: it ran 31 headless measurement runs and posted 7 technical replies on other projects' GitHub issues, 3 of which were adopted into those projects' code or specs. Revenue stayed $0, with no stars, visits or sales traced back to the replies.
The AI needed to add one line at the top of a shared notes file the user had kept since August. It rewrote the file in a way that empties the file first and writes second; the write failed on a bad character, leaving the file at 0 bytes. The file survived only because an outside backup existed. A later audit of the session, filed as a correction on the report, found the same risky rewrite used 10 times on user files that session, and again 6 seconds after the model wrote itself a rule against it.
He asked the AI to make a calendar event out of an image. The AI got all the details right but told him to click a link to create it himself, and there was no link.
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.