| I looked at your solution and extension README, and it's very interesting and well thought out. The fact that you've been using it for six months and that it performs well says a lot. At the end of the day, that's what counts. I like your idea of piggybacking on top of the LSP services, and I can imagine that this was quite a bit of work. Doing it as an MCP server makes it usable across different tools. I also really like the name "Context Master." In my case, it's much more niche since it's for the tool I built. Though it's open source, the key difference is that the "indexing" is only agentic at this point. I can see value in mixing the two. LSP integration scares me because of the amount of work involved, and tree-sitter seems like a good path. In that case, in the code map, for each item, there could be both the LLM response info and some deterministic info, for example, from tree-sitter. That being said, the current approach works so well that I think I am going to keep using and fine-tuning it for a while, and bring in deterministic context only when or if I need it. Anyway, what you built looks great. If it works, that's great. |
I totally get sticking with your current approach. Your workflow sounds very intriguing as well. A combination of both approaches might really be very interesting :) Adding an LLM interpretation layer on top of my graph is also something I'm actively considering.
Thanks for the great discussion, and best of luck with your tool and workflow!