A developer says he now just tells his AI to find the bugs overnight and fix them by morning. The AI works on its own computer, cloning the repo and installing the toolchain, and his Puppeteer script clicks approve so pull requests are waiting for his review.
He had an idea for an NMR experiment he had been sitting on for years. The AI did the literature review, found reference data, ran spin and spectrum simulations, checked if the idea could work, and compared it with other methods, all while he ate dinner and watched TV.
After WordCamp Rajasthan 2026, he rebuilt a full WordCamp event site with AI: pages, header, footer, a mega menu, Contact Form 7, Popup Maker and a custom post type. Six videos show the steps.
As an experiment, the founder told his project-manager bot to ship one secret feature to PromptBase at 4am and deploy it while he slept - the only rule was that it had to benefit the site. Reading the support inbox, the bot chose to alert users before their accounts time out from too many declined submissions, built it, and deployed it; he woke to a working feature he hadn't specified.
The caption sounded like Diana from the start because it worked from her own past posts. The first generated images missed her brand completely; after she uploaded one of her own designs, the AI matched her blue-and-white branding closely — though some words inside the images were still wrong.
This only partly worked. Worth knowing before you try it.
Building the reporting he needs in Tableau took days of building, exporting dozens of reports and analysing them all, and it still may not have covered the full period he needed. With an AI connector, the same job was done in 10 minutes.
He exported 10 hours of his AI usage (8,915 model calls, about 1.15 billion tokens) and had the bot study it. Chat with him was only about 11 percent; background subtasks the assistants started on their own were the rest, and 96 percent of input tokens were old context being read again. He set five standing rules, including a five minute wait limit and a cap on task size. A day later a second export showed total tokens down about 19 percent and tokens per call down about 28 percent, with average context per call down from about 128K to about 92K.
Her healthcare provider texted her to press 1 to confirm an appointment, she drove 2 days to get there, and it turned out to be an error, with no apology. She used three AI tools, mostly the AI in Word, to sue the provider.