Skip to content

Docs/agentdb rag flow#1735

Open
SayanDey322 wants to merge 2 commits into
ruvnet:mainfrom
SayanDey322:docs/agentdb-rag-flow
Open

Docs/agentdb rag flow#1735
SayanDey322 wants to merge 2 commits into
ruvnet:mainfrom
SayanDey322:docs/agentdb-rag-flow

Conversation

@SayanDey322
Copy link
Copy Markdown

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

  • document automatic AgentDB ingestion flow
  • document retrieval via memory_search_unified
  • document RAG tracking and audit visibility
  • document what AgentDB stores

Why

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.

@ruvnet
Copy link
Copy Markdown
Owner

ruvnet commented May 4, 2026

Thanks @SayanDey322. Two things keep this from being mergeable as-is:

1. Scope overlap with #1734

The package.json change (adding "default": "./dist/index.js" to v3/@claude-flow/embeddings) is exactly what #1734 already does. They'll conflict. Please pick one home for that change — most natural is #1734 — and drop it from this PR so this one is purely docs.

2. Duplicate prose in two READMEs

The "AgentDB / RAG behavior" section is added verbatim to both README.md and v3/README.md. Maintaining the same multi-paragraph block in two places is a doc-rot trap. Suggest:

  • Put the full section in one location (probably v3/README.md since it's a v3 capability), and
  • Add a one-line pointer + link in the root README, e.g.
    See [AgentDB / RAG behavior](v3/README.md#agentdb--rag-behavior) in the v3 README.

Once those two are addressed I think the content itself is fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants