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.
The road to a takeoff spot they fly from was not on OpenStreetMap, though satellite images showed the track. They built a tool called osmctl, and the AI drove it and mapped the road.
Hemant Kadam, demonstrating his 'craziest use case' after a couple of days on the AI, opened the app to a Sarvam DevOps Engineer application page. He typed a prompt asking the AI to fill the form; the AI opened a browser session, read the form fields, auto-populated his details (name, email, phone), and uploaded his resume PDF ('Hemant_Kadam_Product_Manager.pdf').
He follows the CNN lawsuit over White House press briefing access. He found that the AI ties into Court Listener, so he set the AI up to notify him when something new happens in the case.
This only partly worked. Worth knowing before you try it.
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.
Shervin Shaikh asked the AI in chat to find any NYC parking tickets under his name and pay them; after he supplied his licence plate, the AI found a $115 'No Standing' ticket in Brooklyn, now $145 with penalties. The first CityPay attempt failed on a billing-address mismatch, but the retry succeeded: $147.90 paid via Stripe Link, confirmed on screen.
A local model helped build a self-hosted services wiki and dataset in an Obsidian vault so his partner could keep systems running if he died, set up in a few hours.
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 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.
His agent reads his email, including PDF attachments, finds the dates and appointments inside, and adds them to his calendar with a check for duplicates. With two kids at different schools sending home a stream of letters, he calls it a big time saver.