In two weeks of real inbox-and-calendar work, The AI Crux had the AI book three conference rooms. Calendar work was functional but conservative: it refused anything outside 9-to-5 local without an explicit override, which the reviewer framed as a guardrail more than intelligence.
A team used an AI 2.5 tool to go through large sets of public comments. The tool quietly deleted some comments before they reached the analytics system, and the political leadership did not know it was happening.
This one went wrong. See what happened before you try it.
After his motorcycle was stolen, his insurer offered nearly half the market value. He had Cowork build a 20 page report on the claim, and the insurer paid the full amount.
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.
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.
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.
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.
Eleanor Konik had the AI and AI team up on dashboards for local nonprofits. The AI did the early research and dug up grant chances the groups had not seen, like a group that pays for field trips to battlefields, a free textbooks program for private schools, and creative arts projects, and the lists were put behind a password for her friends to use.
His morning agent reads his email and builds a prioritized to do list with time blocks for the day. It also checks the weather and warns him to leave earlier when rain would slow his trip, which has twice saved him from showing up soaked.
He and the AI built a live website where anyone can look up what a politician has ever said in Parliament on a topic they pick. He calls it a moral manoeuvrability monitor.
He got the AI to build out a structured dataset of all 4,925 vacancies, with job titles, organisation, salary and location. He shared it in a spreadsheet for other people to play with.
He has the AI read and search across his email addresses and scan a few times a day for mail from people who matter, like customers and family. He has basically stopped checking email forty times a day. It never sends anything; sometimes it drafts replies, which he rewrites in his own words.
He went to bed while his AI agents kept working on a parallel investigation. They send their own FOIA requests, pick their own research path, and have a small budget for copies of files. He set the web permissions for the night before letting them loose.
This only partly worked. Worth knowing before you try it.
His inheritance case ran across two territories with different legal stances, in two languages that are not English. Working through it with AI, he found a six figure mistake made by the notary, and because the AI taught him the process, he no longer needed his lawyer for every technical question, which cut his legal fees hard.
The same setup reads his incoming email and texts, builds his weekly to do list, sends him a digest every morning with the list and any scheduling clashes he might miss, and adds events to the family calendar on its own. A spreadsheet of every house appliance and its service schedule feeds the list, and it drafts the messages to repair firms for him to send.
Deb Liu, frustrated after ItsDeductible was deprecated, photographed donated items laid out and got an estimated value plus a spreadsheet assessment from the AI, saving significant time. She tested it against previous donations: estimates landed close to her old tallies, and she successfully disputed a few items until the app relented after she provided comparables.
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.
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.
This only partly worked. Worth knowing before you try it.
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.
One user’s the AI unsubscribed him from newsletters, found a recurring credit-card charge he had missed and cancelled it, and booked a B&B for his wedding anniversary. Three different errands, one agent, all completed.