Open-source RAG, vector search and agent memory

Retrieval is what stops a model inventing answers about your data. These projects cover the whole path — chunking, embedding, storage, ranking and the memory an agent keeps between runs.

Retrieval stopped being a novelty and became the part of an AI product that decides whether anyone keeps using it. The failure mode is quiet: retrieval returns something plausible, the model writes a confident paragraph around it, and nobody notices for weeks.

The projects here differ mostly in where they put the hard work — some in chunking, some in ranking, some in giving an agent memory that survives a restart. That choice matters more than the vector store underneath, which is close to a commodity now, and it is the axis each description here is written along.

Projects in this topic

21 analysed projects match this topic.

LLM and Claude Tools

Practical simd system built around c++

Skip weeks of custom work by starting from a working simd foundation.

simdc++vectorization
Beginner · Developer library
TOOL-90349View details

Questions people ask

Do I still need RAG with a million-token context window?
Usually yes. Long context solves reading; it does not solve cost, latency or knowing which documents to send. Retrieval remains the cheaper answer whenever the corpus grows faster than the budget.
Which part of a RAG pipeline should I build myself?
The chunking and the evaluation, because both are specific to your documents. Storage and embedding are solved and worth taking off the shelf.
How do I know retrieval is working?
Build a small set of questions with known correct sources before you build the pipeline, and measure whether the right source comes back. Without that set you are judging fluency, not accuracy.

Related collections

All collections

Other topics

Updated: 2026-08-17