Or, By The Sorceries of Python and LM Studio Combined

(Note: this is me rewriting a Claude draft post about this development. I had Claude do the initial draft inside the same chat where most of this python coding had been done).

After I wrote about my n8n automations back in February, my computer died in April, and was replaced by something newer and pinker. I resolved to do something different this time around: without API costs, without cloud dependencies, and without the kind of platform risk that bit me with Perplexity. The goal was to run my automations locally: local models, local inference, local Python scripts. No subscription fees beyond what I was already paying for Claude Pro, no data leaving my machine, no terms of service surprises. I have studied Python, but the actual coding was mostly done by Claude Sonnet 4.6. I’m not including the code itself, because your use cases may be different and your pet chatbot is probably just as good at writing python scripts as mine.

What follows is a report from the other side of that transition. TL;DR version: you can get an AI chatbot to write and troubleshoot python scripts which talk to LM Studio and do various useful support tasks for writers. Once those python scripts are finalized, you will be that much less dependent on the chatbots living out there on other people’s servers. Your “Skynet Secretary” will be living at home with you, instead of out there online. I also include some asides on how to do something similar with just a chatbot and without the python scripts and LM Studio, for people who care more about keeping things simple than keeping them local.

Continue reading “AI as Writer’s Assistant: the Local Edition” →