What specific problem does this solve?
- Amazon Bedrock provides several different APIs depending on what you're trying to accomplish.
- Amazon Bedrock supports a feature called "Knowledge Bases" (Retrieval Augmented Generation (RAG))
- AWS customers can import custom documentation ("knowledge") via S3, and Bedrock will generate embeddings and store in a vector database
- Roo Code supports Amazon Bedrock as a LLM provider, however .....
- Roo Code does not [appear to] support the RetrieveAndGenerate API
- The
RetrieveAndGenerate Bedrock API would enable Roo Code users to query information stored in Bedrock "Knowledge Bases" and enhance the responses they receive
I searched for any mention of RetrieveAndGenerate and didn't see anything, so based on that, I believe this is a unique suggestion.
In general, I would flag this as a low-priority, nice-to-have feature. Roo Code already works exceptionally well without it.
- Who is affected? Anyone using Amazon Bedrock with Roo Code, and is interested in using RAG.
- When does this happen? During any invocation of a LLM, answering questions, generating or architecting code, etc.
- What's the current behaviour vs expected behaviour? Answered above.
- What's the impact? (time wasted, errors caused, etc.) Opportunity to enhance accuracy of LLM responses by adding RAG into the mix.
Additional context (optional)
No response
Roo Code Task Links (Optional)
No response
Request checklist
Interested in implementing this?
Implementation requirements
How should this be solved? (REQUIRED if contributing, optional otherwise)
No response
How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)
No response
Technical considerations (REQUIRED if contributing, optional otherwise)
No response
Trade-offs and risks (REQUIRED if contributing, optional otherwise)
No response
What specific problem does this solve?
RetrieveAndGenerateBedrock API would enable Roo Code users to query information stored in Bedrock "Knowledge Bases" and enhance the responses they receiveI searched for any mention of
RetrieveAndGenerateand didn't see anything, so based on that, I believe this is a unique suggestion.In general, I would flag this as a low-priority, nice-to-have feature. Roo Code already works exceptionally well without it.
Additional context (optional)
No response
Roo Code Task Links (Optional)
No response
Request checklist
Interested in implementing this?
Implementation requirements
How should this be solved? (REQUIRED if contributing, optional otherwise)
No response
How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)
No response
Technical considerations (REQUIRED if contributing, optional otherwise)
No response
Trade-offs and risks (REQUIRED if contributing, optional otherwise)
No response