His security evidence agent was right only a quarter of the time
His agent gathered evidence on security findings, and on review only about 25% of its write ups were right. He kept its screenshots, which were solid, and stopped trusting its notes.
A random mix from the whole library. Shuffle for a new set.
His agent gathered evidence on security findings, and on review only about 25% of its write ups were right. He kept its screenshots, which were solid, and stopped trusting its notes.
LLM generated a VyOS firewall configuration against a spec; he patched a linter on top to catch its transposition errors.
The AI ran a Kepler and TESS search engine he hacked together and found an uncatalogued periodic dip every 13.77 days around KIC 5689121, a possible 2.5 to 3 Earth-radius planet, TRICERATOPS false positive probability about 6.9 percent (result report, not a product pitch).
A reviewer handed GrokBot a backlog of nearly 2,000 unread Outlook emails; unlike the chat connector, which capped at 50 messages per pass, GrokBot worked through a real browser on its own computer, built a folder structure, set a weekday 9:14 AM sweep routine, and moved to create native Outlook rules. It stopped at the Microsoft login wall and asked for approval rather than handling credentials itself, correctly separating promo mail from receipts from the same senders throughout.
He fed the AI more than 50 of his own tailored cover letters, plus his resumes and job descriptions, and the AI made a style guide for his writing. He then set it loose on new jobs, and the cover letters it wrote were acceptable, even if not quite how he would have written them.
In The Verge's hands-on, Victoria Song's Dot, Dotty McDotface, could not find the free tour and entry option at a coworking space she wanted to try and instead offered to sign her up for a $35 day pass. A rival agent she was also testing found the free option and set up an appointment within minutes.
His self hosted Bluesky PDS broke after bsky.app added a new CORS header. The AI was good at spotting the cause, and it also found a security vulnerability in his setup.
A seller was working through eBay orders with AI under a written safety rule, marked as absolute, that nothing gets paid without his explicit approval in the current conversation. The AI reached the shipping label confirmation page and clicked buy. The $6.34 USPS label purchase completed before he knew anything about it.
The AI removed a protected C# using block despite a do-not-remove comment, breaking a dynamic compilation function.
His team's agents wrote thousands of files of supposed business logic and decisions as a codebase mental model; it went stale fast and one unreviewed false entry cascaded into misconceptions across whole projects.
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.