Thank you for checking out VT Code! Yes, VT Code supports connecting to local LLMs through two main providers: LM Studio and Ollama. But local LLMs inference is experimenting, as I don't have enough hardware with large VRAM to test it. Though some users have asked for it. And my initial vision is to support open weight and local inference. So LM Studio and Ollama are supported but still have bugs. https://github.com/vinhnx/VTCode/blob/a154162f/docs/provider...

Notes: VT Code also supports custom OpenAI-compatible providers through the custom providers' configuration, allowing you to connect to any local LLM server that exposes an OpenAI-compatible API: https://github.com/vinhnx/VTCode/blob/a154162f/docs/config/C...

Thank you for checking out VT Code! “LLM-native code understanding” refers to VT Code's approach of using LLM as the primary mechanism for semantic code analysis rather than relying solely on traditional static analysis tools. I have tried using ast-grep for structured code parsing understanding as a ground truth before/after the agent executes a code analysis or does a code edit/write operation and code context understanding and symbol analysis. I also tried to use tree-sitter to enhance the user's prompt parser grammar. Example: currently I use tree-sitter bash grammar to check for user input prompts for Unix commands: “run cargo fmt” -> VT Code will detect and understand right away the intent is to run a bash command -> parse and hand it to the harness -> wait for the stdout/err and then handle to the llm as an agent loop. This is to save context and parser roundtrip.

This is just my naive implementation, so as “llm-native code understanding,” VT Code will use LLMs to perform deep code understanding across multiple programming languages as a fallback if my enhance `ast-grep` + ripgrep + tree-sitter implementation is failed, but this relies on the model's intelligent.

Note: I don't have many words to describe this cleanly, but initially when I designed and built VT Code, I had a vision of using `ast-grep` and `ripgrep` and `tree-sitter`, for AST-enhanced grep code for replacement of std grep (I also use my grep tool, called `perg`). I also wanted to parse source code into concrete syntax trees usable in compilers, interpreters, text editors, and static analyzers. Also, I thought of using LSP but still exp. All this might be overhead for a small open source coding harness, but I love to build, so I thought to myself, why not, just build and learn.