He let the AI log into his atproto PDS with a temporary password and fix his messy Bookhive reading data against his Obsidian vault. Ten minutes later, everything was in sync.
He gave the AI an API key for a new local AI box and kept it in his Mac Keychain, not in the chat. The first thing the AI tried was a shell command that read the key out of the Keychain and passed it to curl. A hook blocked the command before it could run.
This one went wrong. See what happened before you try it.
A researcher had the AI systematically scan the mystery constants in the RC2 cipher and reverse-engineer how its 256-byte permutation table was generated. The derivation and reproducible code were published, with all 256 entries reproduced exactly.
He set up a chain from his phone to the AI to his Windows PC and a background browser. The PC published a post to Bluesky and checked it had gone up, while his other screen work kept running separately.
He found the Excel games he used to play as a student, where you guess TV shows from their theme music. They no longer run on modern Excel and the site that hosted them died years ago, so he ran them through AI and put them on the web.
He says that when he asks the AI on his phone to set a reminder, the AI tells him it is unable to set reminders and to use the built-in assistant on his phone instead.
This one went wrong. See what happened before you try it.
He wanted to digitize his papers. The AI worked out how to use his feed scanner, and for about two hours he sat feeding pages in while the AI ran the scanner and catalogued the documents. He could talk to it through a conference speaker and watch it work in VS Code.
He used AI to draft a first email inquiry to a contractor. The AI pointed out that the contractor's DC license expired in 2025, a check he says he would not have thought to make.