I just re-enabled the MCP in Tinderbox - I typically work with two different documents at a time, and know it can be confused switching through the MCP server.
This time, I opened one document (a literature map); Claude suggested I installed an Applescript MCP server, gave me the JSON and the path to edit, and then asked me to restart it, so it would be able to access the second document through Applescript, while working in the first. I did so; it’s now comparing items in both documents.
Dear god. I mentioned Bookends to Claude and it got my entire reading list out through some AppleScript it debugged on the fly. It’s now adding titles I’m missing to a Tinderbox file, and wrapping them in adornments. It seems disappointed that ‘Lavender’ wasn’t a recognised Tinderbox colour.
I’m kind of lost for words. If there was any sense this would have been possible in the years before Covid, it would have been laughed off as a 70s sci-fi delusion.
Yes, it’s wild. And wonderful. The AI is also often fallible.
I spent the afternoon working on a very difficult Tinderbox bug that I knew would be a real headache, and that starts from some JSON that @TomD found in the wild. So, the first order of business was to find out just exactly what, in this unholy morass, started to cause trouble. We’d take out this hunk: still bad! This other hunk? It’s good! So the problem’s got to be there. And so forth, for hours.
Claude kept saying “Oh, I’ve got it now!” and charging off to read the code. The first time I let it go for 15min before interrupting. After that, it had a shorter leash. “No, don’t hare off after interesting code. I really want to isolate the problem, and I never did like psychic bids in contract bridge!”