A random mix from the whole library. Shuffle for a new set.
He helped his brother with the website of Ichtus Vlaanderen, an NGO he used to work for. Using the AI through the WordPress.com MCP connector, he fixed design problems like a messy photo section and buttons that were too big.
Around Elmira and Corning, New York, event listings were scattered across library systems, a brewery site, a school app, chamber newsletters and Facebook, so people found out about things the day after. He had the AI build one page that checks 101 sources across three New York counties and part of northern Pennsylvania: 1,855 listings over the next 90 days, 1,767 events after duplicates are merged, about 250 in any week, at 159 venues. A cron job reruns it every six hours on cheap shared hosting, about 8,300 lines of PHP, and cancellations mostly handle themselves because an event disappears when its source stops listing it.
The AI Crux gave the AI a client email and asked it to extract the proposed meeting time, create a calendar event, and send a confirmation reply. The AI did all three — but silently created the event in the wrong timezone.
Volunteered and built a cartography data pipeline with coding agents for an educator, integrating sources updated every few minutes so new maps appear within about 5 minutes on a low-powered machine.
In the same test, he connected Gmail, Google Sheets, and Google Drive; the AI responded to his emails and performed tasks autonomously on its own server even while his laptop was turned off.
Ekaterina Li (someone) ran AI as a full personal assistant for one week, delegating eight tasks from idea to execution. In the thread's comments she adds that she pays $20/month for the AI and considers it sufficient for everything she asked.
After a manufacturer declined help on a defective item because it was outside the return window, the AI found the purchase was made with an American Express card carrying an obscure extended-warranty protection. It submitted the claim on the author's behalf and obtained the refund.
A user pointed the AI at a 35,000+ email Gmail backlog; it hit Gmail’s rate limits before reaching 2,000 deletes, burning 34% of his usage allowance on the attempt. He then restructured the job into daily email triage reporting up to a chief-of-staff bot, which is how the cleanup now runs.
His inbox gets so much mail that about half of what matters was being missed and a quarter sat in spam. His AI watches the box, sorts what is important, and messages him in a separate chat when something he cares about lands; it took a while to tune the prompt before it matched his judgment.
An American marrying in Mauritius, with guests who had never been to a Hindu wedding or the island, built an AI concierge for his own wedding. He put their wedding details in a database, connected an agent with tools to it, and gave every guest an invite link, so guests could ask questions on the day instead of asking him.
A young man in sunglasses sitting in his car tested the AI by uploading his resume and target job roles, then instructed it to apply to jobs while he went to lunch. Screen recordings showed multiple browser tasks running and a notification confirming an application submitted to 'ioTech Solutions.' The AI asked for information once for the first application, then reused it — resulting in 50 applications submitted while he was idle.
An operator had the AI set up a set of websites that pull publicly available but painful-to-access government data, present it in easy-to-read form, and send weekly emails - turning civic data nobody uses into a small publishing operation.
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.
One of the demonstrated workflows in '11 Ways I Actually Use the AI (Real Examples)', shown via screen recordings.
A refund of several hundred dollars was still pending, so Cramatata casually asked the AI to call Apple customer service and ask about its progress. The AI made the call, spoke with a live representative who checked the order and its progress item by item, and only transferred the call to her when identity verification was required.
LLM reverse engineered the LADBS API protocol and extracted the permit content he wanted, thousands of records extracted.
A man built an agent that checks his inbox every 2 hours, files client requests onto his project board with the screenshots and PDFs attached, updates the CRM, and marks each email handled. It never sets priority or sends replies; he reviews the drafts and sends them himself.
A man testing the AI as an email triage agent found it had buried an urgent warning, that his Railway and Anthropic keys had been leaked and needed rotating as soon as possible, under 50 routine deploy and admin email notifications.
Before a speaking engagement, Ulanoff couldn't recall where he was talking or where to park. He asked the AI to find the original note from his contact, misspelling the contact's name.
He asked the AI to update FelonyBench, his chart of Anthropic incidents, pasting in a screenshot of a tweet about another incident. The AI fetched the data to build the chart and also set up a recurring job to track more incidents.
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.