Making Clear What You Are Actually Doing Here #57

Activity

1. Davidyz commented on Apr 2, 2025

   

   Davidyz

   on Apr 2, 2025

   Owner

   More actions

   Hi, that's a fair question for both potential contributors and people who want to know this for privacy reasons. I'll begin by admitting that the documentation isn't the best, partially because I didn't expect so many people to be interested in this. I'll explain the whole process (vectorise and query) here so that you (and other people interested in this) can have a better idea about what happens behind the scenes and any privacy concerns that you may have.

   This project uses ChromeDB as the backend. It's a vector database that stores the embedding vectors. It contains some telemetry (which I tried my best, from my end, to disable). It handles the storage and retrieval of the data. For each project, vectorcode creates a new collection for it and puts all embeddings for this project in this collection. This isolates projects from each other so that your queries are project-specific.

   When you vectorise files, the files will first go through a chunker that splits large documents into smaller pieces so that embedding models can properly handle them without losing too much information. There are 2 different chunking strategies for files:

   1. Character-count-based naive chunking: evenly split the file into chunks by character counts. That is, if the chunk_size option is set to 2500, the chunker will yield a chunk for every 2500 characters in the file. This also implements an overlapping mechanism (the overlap_ratio option), which helps prevent the loss of information due to splitting texts from mid-sentence;
   2. Treesitter-based semantic chunking: If vectorcode managed to guess the filetype for a file (based on the filename suffix), it'll use treesitter to traverse the nodes in the AST and split the source code (by nodes in the AST) into chunks. This is also bound by the chunk_size option. This chunker is more likely to produce semantically meaningful chunks. If vectorcode fails to guess the filetype, it'll fall back to the naive chunking mentioned above.

   You can preview the chunks by running vectorcode chunks path_to_file. This will invoke a chunker and output chunks in the way they would be chunked when added to the database.

   As for embedding, Sentence Transformers is chosen mostly because it's easy to use. It's not only for natural languages, and there are models supported by sentence transformers that specialise in code embeddings. Also, using an embedding function that works for natural language means that you can vectorise documentation and doc strings. This makes the embedding model more generalisable than a model that only uses AST. The following is a screenshot of me using codecompanion.nvim + VectorCode to talk to an LLM about the ArchLinux Wiki (installed locally from this package).

   
   you can do the same on neovim documentation or even this repo.

   Sentence transformers are also not your only option. Any embedding model supported by chromadb should work (although I've only tried sentence transformer and ollama), so you have the option to switch to your own choice. I was quite limited in terms of compute power (2c4t with no discrete GPU), so I didn't have the opportunity to experiment with more embedding models, so I can't comment on the effectiveness of using alternative embedding models for now, but I will do that once I can run some evaluations on better hardware.

   When making queries, the query messages will be chunked too (if they're too long), using the naive chunking method. Each query keyword (or chunk) will get its own best-matched chunks. Each of the ${(\text{query}, \text{chunk})}$ pair will be assigned a similarity score. Since each vectorised file may correspond to multiple chunks, the similarities will be averaged for each file (with outliers removed) to produce scores for each document. The score is either produced from a reranker model or simply using the distance returned by chromadb. The relevant source code is here.

   I hope this answers most of your questions.
2. Repository owner locked and limited conversation to collaborators on Apr 2, 2025
3. Davidyz

   converted this issue into a discussion #58 on Apr 2, 2025