Build a documentation chatbot that answers user questions more accurately than standard RAG.
Index a documentation website by crawling it and generating searchable questions per section.
Run a fully local retrieval pipeline using Ollama with no cloud API keys.
Compare retrieval quality between question based indexing and raw text chunk indexing.
| ameghcoder/qindex-rag | 1038lab/agnes-ai | 3eyedtiger/video2vrcemote | |
|---|---|---|---|
| Stars | 4 | 4 | 4 |
| Language | Python | Python | Python |
| Setup difficulty | moderate | easy | easy |
| Complexity | 4/5 | 2/5 | 1/5 |
| Audience | developer | vibe coder | vibe coder |
Figures from each repo's GitHub metadata at analysis time.
Needs a running Qdrant instance via Docker plus either OpenAI and Anthropic API keys or locally pulled Ollama models.
QIndex-RAG is a system for building a question answering tool over your own documents, using an approach called retrieval augmented generation. The usual version of this approach stores chunks of document text and tries to match a user's question against that raw text, which often fails because people phrase questions very differently from how documentation is written. QIndex changes this by having an AI model generate a list of likely questions for each chunk of text when the documents are first processed, then storing those generated questions instead of the raw text for matching. When a real user asks a question, it is compared against these stored questions rather than the original prose, which the project reports produces much better matches. Before generating questions, the tool splits documents in a way that respects their structure, first by headings, then by paragraphs, and only down to individual sentences if a paragraph is still too long. Short pages are kept as one single chunk. Each chunk also gets a short summary of its source page attached to the front, so it still makes sense if it is read on its own later. Generated questions are checked against the chunk they came from and thrown out if they do not share enough real words with it, which helps prevent the system from inventing irrelevant questions. The README includes a comparison table showing this approach scoring notably higher on matching queries to the right page than a standard chunk based approach in the author's own tests against a real documentation site. The project ships two versions, one that uses OpenAI and Anthropic cloud APIs for embeddings and question generation, and a fully local version that runs through Ollama with no API keys required. Both store the question vectors in a Qdrant database, which can be run locally with Docker. Setup requires installing Python dependencies, a Playwright browser for crawling documentation pages, and either API keys or locally pulled Ollama models depending on which version you use.
A retrieval augmented generation tool that indexes AI generated questions instead of raw text chunks, so user questions match more accurately against your documents.
Mainly Python. The stack also includes Python, Qdrant, OpenAI API.
The README does not state license terms.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.