A random mix from the whole library. Shuffle for a new set.
Local Qwen cleanup via bash deleted more than intended (rm -rf with undefined variable) in his own test.
Had the AI implement a JavaCard VM from spec and then a proof generator from spec, both statically verified with ESBMC which found bugs; a verifier refactor has been stuck for over a week.
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.
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.
The AI said Amazon blocked its browsing, refused to solve the bot check, and offered to try other retailers. Amazon shopping was 'off the table' in her tests.
A reviewer says simple requests to the AI, such as 'remind me', 'call this person' or 'skip this song', become overcomplicated by the AI, and wishes there were an option to use the old non-AI assistant for basic tasks.
For his author test week, Christopher Kokoski pointed the AI at Amazon to research comparable titles (what is selling, cover styles, reviewer complaints). Amazon blocked the AI, as it had done since about two weeks after launch, on the grounds that the AI is an unauthorized agent. Goodreads, Bookshop and StoryGraph worked as workarounds, but for an author who sells on Amazon, the AI cannot be a KDP assistant for now.
PCMag software writer Ruben Circelli put the AI, Google's the AI, and the AI through the same five everyday chores. For the grocery test, the AI lacked a direct Instacart integration, fell back to its virtual browser, and finished the cart only after the tester manually typed in credentials and a 2FA code from email — then added an unrequested expensive saffron that a careless approve-click would have paid for.
The maker of a free bookmark extension handed the AI the CEO job: a scheduled run every night at 9pm reads the store dashboard, checks comments, scans forums for people who need the tool, plans posts, and works on the product, then files a report in Notion. Nothing public goes out until he replies go. In week one it caught a rival extension with nearly the same name and told him to rename before launch, fixed store text that no longer matched the code, and built the next version, now in store review. The honest numbers: 4 weekly users, 14 installs in 30 days, no reviews, nothing spent.
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.