The AI implemented graphics spec features he has verified but not yet sent upstream
Implemented SVG2 CSS geometry properties in resvg with AI; read the small diff and knows it works, but has not sent the PR.
A random mix from the whole library. Shuffle for a new set.
Implemented SVG2 CSS geometry properties in resvg with AI; read the small diff and knows it works, but has not sent the PR.
Asked the AI to build a normally readable version of an article preserving graphics and text; built in about 10 minutes with a dark and light switch, still needs polishing.
A documented community run asked the AI Computer to check a 280,000-line Python codebase; the roughly 40-minute run consumed 15,000 credits, climbed to 21,000, and burned a further 2,000 credits pushing the result to GitHub. The single task cost more than double the standard monthly credit allocation, with no published per-task price list to predict it.
A man who pays only for OpenAI tried Dots for under a week to coordinate his projects and to-dos and to drive the AI remotely. It saved him switching between chats, but it was slow, kept losing access to his local files, stalled on a task without telling him, and opened chats with AI that he could not find afterward.
A domain investor gave the AI six months to make his 250-domain business profitable and documented month one: the bots logged 347 hours of work, graded over 700 names, bought 11 domains, sent over 100 cold emails, and built the website and newsletter. Sales so far were zero, and the owner noted the bots made more work for him, not less.
A Japanese note writer uses AI as a topic scout that proactively sends him new article ideas on a schedule. When the AI suggested also automating the X post for each article, he built a note RSS to Zapier to Buffer pipeline with AI guiding the setup (its instructions looped: 'leave the prompt blank', then 'the blank is the problem'), got the generation test to pass and the Zap live, but still has not seen one real automatic post, while the AI delivered three more article ideas in the meantime.
Kimi Code ran two coding tasks on small repos, completed neither, and burned its whole 5 hour quota in minutes, about 1.37 dollars of API-rate usage across 1.59M tokens in the logs.
He follows the CNN lawsuit over White House press briefing access. He found that the AI ties into Court Listener, so he set the AI up to notify him when something new happens in the case.
He used AI in a Google spreadsheet to apply a mass change to 30k rows. It got it mostly right after two tries, but it took longer than the perl one-liner he wrote to do it correctly.
Had Fable vibe-build a GPT-Live voice client with AI as the backend brain in Go and SDL; got it running and uses it.
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.