Live page 🚀 : https://shreyas-girjapure.github.io/Salesforce-CLI-RAG-Bot/
Document search implementations generally involve
- Data Splitting ✂️
- Embedding 🧵
- Storing in Vector DB 💾
- Retrieving with LLM's layer for summary.🕵️
There are some major inaccuracies in search results depending RAG strategy and dataset used. Below are some areas which contributes to inaccuracy.
- Data splitting
- Chunked data may lose important context for the query. Retrieval of such data generates bad results in final outcome.
- LLM's layer
- LLM some times add their own flavors
hallucinations
on vectored context provided.
- LLM some times add their own flavors
So by avoiding standard split and embed
approaches and fine controlling the dataset , Better results can be achieved.
This project is implementation of such finely controlled dataset's RAG strategy.
Tip : You can easily create and host simple AI powered bots using low code tools like
1. RelevanceAI
1. Flowise
- Overcome inaccuracy of simple RAG strategy and provide accurate results.
- Implement concepts like
RAG
,Vector DB
,LLM Monitoring
using lang-chain JS. - Always wanted a personal AI powered
RAG bot
😁.
- Actually read through Salesforce CLI Reference Documentation
- Use
sfdx search
command for keyword searching commands.
- Visit 🚀 RAG Bot Page for salesforce cli documentation searches.
- Search for any thing related to salesforce CLI.
- Semantic search over large document.
- High accuracy and complete context in results.
- Answers* unrelated questions to the context used.
- Has support to load local vector stores for faster retrieval.
LLM Monitor
support for token and LLM analytics.- Around
0.5
seconds for Salesforce CLI Document related searches. 5+
seconds for Non Salesforce CLI Document related searches.
- AI is not magic , lot of guard rails and code alterations are needed to have a useful AI bot which doesn't hallucinates much.
- Understanding your own dataset is really important before choosing approach for RAG bot.
- Adding chat bot layer over large documents will only improve current businesses and user experiences.
- This is a simple lang chain based implementation of some AI concepts. Lots of improvements are needed. Feel free to contribute 🥳
- Free Server has cold start issues. May face delays in searches due to server inactivity.
- No Rate guards are placed in code , prone to credit loss or server crashes 😭.
RPM : 3,500
TPM : 90,000
- Since documentations has 2 sections of same semantic commands , deprecated commands may be retrieved.
- Example : When you search for
How to login
, vector search might retrieveauth web login
section orsfdx force auth web login
. - Similarly for deploy commands and other similar commands from
sf
andsfdx
section.
- Example : When you search for
Allowed Requests Per Minute : 3,500
- Current implementation does not involve agent-ish implementations , so RPM limit should be very tough to reach for current project scale.
Allowed Tokens Per Minute : 90,000
- Single requests cost around 1000-3000 tokens , So to exhaust daily limits more than 30 requests have to be made in a minute.
- UI is very poorly designed 😑.