He built geo-v.eu, a live calendar of EU political and economic events that runs to 2028. The AI Haiku judges each candidate event against his written editorial standard, the pipeline hunts for the outcome for five days after each event, and the site rebuilds daily from static files.
Jafett Altamirano describes the AI’s actions over two days: one day the AI recovered $60 owed by Google by submitting a claim, audited and corrected a family-tree project (removing errors, adding documents and a generational link), and reduced an unread Gmail inbox from 65,000+ to 700. The author emphasizes all of this was free.
Someone posted an illustration styled as an iPhone call-history screen showing seven missed calls from unknown/spam numbers over three days (fictional numbers noted). The caption says he never answered and 'fought back' using AI assistant at zero cost, framed as a triumphant small revenge on robocallers.
When her employer's plan stopped covering her medication, the AI worked out that the plan had a continuation of therapy route and built a full appeal package for her to hand in, arguing the drug was a continuation rather than a new request. She filed it, and her doctor used the letter template it wrote.
This only partly worked. Worth knowing before you try it.
Rachel D. Gainsbrugh (someone, ~3.5K followers, AI/systems creator) signed up for the AI on Sept 13, 2026, connected her calendar read-only, and typed six standing errand rules once — including a 7:05 AM daily calendar scan that flags overlapping meetings or ones falling inside a flight — then handed it two long-dodged errands (an appointment blocked by a flight, a subscription update).
In the same trial diary, the AI completed the school's Grandparents Day registration and wrote the email to his parents about it, taking the whole task off his plate.
Outside code, his biggest win is boring paperwork. The AI filed his reserve duty refunds, sorted out his national insurance payments and did his flight check-ins, working in his own logged in Chrome. Each job is about ten minutes of work, which is exactly why he kept putting them off. He gives each area of his life its own folder with a CLAUDE.md and a notes file, so the money stuff does not mix with the rest.
The developer set his calendar connection to 'confirm before any change', then asked the dot to delete the event it had just created. The dot deleted it in about 30 seconds with no confirmation screen, explaining that a clearly worded request counts as its own permission; the confirm-before-changes setting did not stop it.
This one went wrong. See what happened before you try it.