My AI setup, part 2: Byzantine

tag(s): #failures #programming #overblown-minor-annoyances Here is a link to part 1. If you don't feel like reading it: I had an LLM write a minimal MCP server to expose Emacs, and I figured if I am going to use these tools, at least make them work in a way that I enjoy. So I kept iterating on that initial setup. Tools maturing A couple weeks ago I felt like I needed to change the name of the mincp repository. For starters, it wasn't minimal anymore. And also, it morphed so much. It went from "let Claude run an couple Emacs commands" to a complete workflow that uses Emacs as the duck tape connecting file system and database access, code reviews, and even JIRA connectors. It really is a unique setup, not unlike my """blogging platform""". Someone looking at the repo might encounter ideas to copy, but I would find it hard to believe that anyone else in this planet could use it as-is. That's how tailored it is. But before disclosing the name (which is in the title of the post, anyway.…