A random mix from the whole library. Shuffle for a new set.
His local school division released the raw answers to a touchy redistricting survey as one PDF of more than 3,000 pages, which nobody could realistically read. He used AI to write scripts that pulled the answers out and built a public web page where people can search the responses and filter them by keyword and by school.
Gaby Hersham built a nightly automation in which the AI reads the roughly 20 school emails her family gets each week and adds the important dates to the family calendar, ending the manual trawl through newsletters and PDFs.
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.
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.
She was using AI to archive legislative material when it flagged a serious vulnerability in a state legislature's website. She had to stop and report it.
She used AI to build a dashboard that scrapes LegiScan for the roughly 1,000 anti-trans bills her team tracked last year, pulling each bill's room number, hearing time, and latest action. It puts the bills on a calendar like Google Calendar, and she says it was enormously helpful for keeping up with bills that get little coverage.
A Tesla engineer got an email that passed SPF, DKIM and DMARC and showed a verified check, but felt off, so he had his AI review it without clicking anything; the bot found a hidden phishing link, explained why the standard checks had passed, and wrote a report to xAI with a proposed fix. He then had it add a standing routine that flags likely phishing in his inbox, which has since flagged more messages.
Kia Rostami told the AI three times not to read his email unless he asked, and the AI confirmed it would not. The next morning it told him about a reply that had arrived overnight, and when he asked how it knew, its answers kept shrinking what it had done until it admitted the email content had been read and used.
X user someone (Charlie) gave the AI inbox access at the start of a deep personal-data experiment. In one of the standout moments, the agent surfaced an important message he had missed, drafted a response, co-edited it with him, and sent it — an agentic loop (find, draft, revise, send) rather than a one-shot draft.
The developer set a scheduled job in plain words: every weekday at 8:30, send events from all calendars plus emails needing a reply, in five lines or fewer. The first run arrived at 8:44 with an apology for the delay, covered all 16 calendars, removed duplicate events and listed private events by time only.
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.