Retrieval-augmented generation, RAG, is the pattern of fetching relevant content at request time and putting it in the model's context before it answers. Documents are split into chunks, each chunk is embedded into a vector, and the chunks sit in an index. At request time the question is embedded the same way, the index returns the closest chunks, and the model generates its answer from what came back.
It helps an agent because a model's weights hold only what it was trained on, and context windows are finite, so an agent can't carry its whole knowledge base into every request. RAG hands it exactly the slice a request needs, from internal docs, past tickets, or a product catalog, without retraining anything, and the corpus can be updated at any time.
RAG is bad at questions whose answers aren't localized in a few passages. Retrieval returns a top handful of chunks, so anything that needs aggregating across many documents, counting, or summarizing a whole corpus won't work. It's also weak when the question's wording doesn't resemble the document's wording, since similarity search leans on phrasing. And when the corpus holds stale or contradictory content, the model will faithfully answer from the wrong version.
11 questions
Answered, plainly.
Two ways to run Tessary.
Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.
Tessary Cloud
We host it for you. Send your first trace with nothing to deploy and no model key.
- traces
- 10,000 per calendar month
- stored trace data
- 1 GB
- retention
- 30 days
- model credit
- $10, one-time, for triage and root-cause analysis
- credit card
- not required
Self-hosted Tessary
Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.
Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md
docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y