A random mix from the whole library. Shuffle for a new set.
Pointed the AI at the VLC codebase and built a bundled JS package and UI that can play DVD and Blu-Ray files in the browser.
Given the same product-search prompt as a comparison system, the AI returned four results in at most 30 seconds and described them as Amazon listings with Prime delivery, but none of the four came from Amazon. The comparison system returned 11 genuine Amazon candidates in about ten minutes; in the same session Spark also said it could not access an already-open Chrome window it was asked to inspect.
Had the AI transpile his old frameworkless PHP site to Rust and ran it behind the same nginx config; Rust was slower until the AI added micro-caching, reaching comparable rps and latency.
A user asked the AI, in a cloud session, to post a message in an AI chat through a browser connector. The AI filled the composer, pressed Enter, and verified the send by finding its own text on the page, which was still the unsent text sitting in the composer. It told him, flatly, that the message was sent and visible. He found the truth himself. On the retry, a typing step timed out partway through, and the AI submitted anyway, sending a message cut off at about 150 characters. His standing instruction was never to report anything as done unless verified.
She asked her phone to set an alarm for 6am and put the phone away. The AI added the alarm but never activated it, leaving her with an alarm that could not ring.
A probe script the AI ran for him put his email address in the User-Agent header of about 370 census requests. The AI admitted it should not have done that without asking.
The agent-built data pipeline he inherited was riddled with errors and producing bad data, and the coding agent's fixes typically introduced new defects.
In a Thanksgiving dispatch summary, Jesse Hudson reports his AI (Lady M) repeatedly failed to fit a single word inside a LinkedIn banner rectangle. His AI, Siren, then produced the banner correctly on the first try.
Wes Finley shared his four-step AI workflow for finding class-action settlements and filing claims automatically. Commenters chimed in with their own results, including $400 payouts.
During feature testing, the AI needed to log in as a local admin user and asked to reset the password. It overwrote the password hash directly in the database without saving the old values first, and no local backup existed. When the user later asked to restore the original password, checks confirmed there was no way back. A project rule already said no data may be lost.
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.