Docs/agentdb rag flow#1735
Open
SayanDey322 wants to merge 2 commits into
Open
Conversation
Owner
|
Thanks @SayanDey322. Two things keep this from being mergeable as-is: 1. Scope overlap with #1734 The 2. Duplicate prose in two READMEs The "AgentDB / RAG behavior" section is added verbatim to both
Once those two are addressed I think the content itself is fine. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds documentation explaining how agents ingest project context into AgentDB, how retrieval is performed, and how users can inspect RAG usage in current releases.
Changes
memory_search_unifiedWhy
The functionality already exists in current releases, but it is not easy to discover from the current docs. This improves clarity without changing runtime behavior.