You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ChatCraft has been expanded to include File Attachments and DuckDB, which supports querying files. The two features have been connected, so you can attach files, run SQL queries on them, get back results, download them, etc.
Now that we have this foundation, I think we have most of what we need for building a RAG solution, when file attachments are too large to put into the chat context.
I think the process would work like this:
user attaches some files with text we can extract (PDF, source code, Word Doc, etc)
somehow (UI? automatically based on file size) we decide when use these file attachments for RAG vs. embedding directly in the chat messages
we take the set of RAG-attachment-files and "index" them in DuckDB. Maybe we use full-text search or maybe we use vector search (see part 1, part 2)
when the user asks a question, we use their prompt to create a query, get back results from the indexed docs, and include relevant text context along with the original prompt
The initial version of this can be crude, without proper UI, optimal indexing, etc. We need to play a bit to get this right.
Likely, the best way to begin this work is to prototype it outside of ChatCraft using DuckDB and text files locally.
The text was updated successfully, but these errors were encountered:
ChatCraft has been expanded to include File Attachments and DuckDB, which supports querying files. The two features have been connected, so you can attach files, run SQL queries on them, get back results, download them, etc.
Now that we have this foundation, I think we have most of what we need for building a RAG solution, when file attachments are too large to put into the chat context.
I think the process would work like this:
The initial version of this can be crude, without proper UI, optimal indexing, etc. We need to play a bit to get this right.
Likely, the best way to begin this work is to prototype it outside of ChatCraft using DuckDB and text files locally.
The text was updated successfully, but these errors were encountered: