Elm module size was a problem until I started using Serena, which provides more surgical search/read/edit tools as an MCP. The Claude Pro got a 1M token context size which solved the problem a different way. More recently I have noticed CC is not really using Serena any more, I think maybe it got its own more surgical tools for large files. I don’t think large Elm modules is a problem any more, at least not for Claude Pro.
Does look interesting though, this PAI thing.
I created this RAG tool for setting up a RAG from the command line on a file pattern glob: https://github.com/the-sett/rag-cli
That has been my approach to creating “personal AI”. Get a bunch of files on some topic of interest, RAG them, then fire up the chat UI.
My eldest son is sitting his school exams currently, I downloaded all the syllabus and marking info and past papers from the official exam bodies website, and made him a personal AI for each subject. There are agents described that will run quizzes and then mark his answers to the exam bodies guidelines standards, and tell him exactly what he lost marks on and how to get from there to full marks.
One issue I had recently is that I use this to work with code. I noticed that AI kept saying, this won’t work for your code because you have a custom Thing implemented, so the out of the box technique for this library is being bypassed meaning you cannot do… It kept saying this even though I had removed the custom Thing long ago. Was still there in some of my docs! So I wonder, personal AI with memory sounds good, but what about when memories are no longer valid - how do you remove them or otherwise mark them as no longer current in a way that AI will be clear on ?